Skip to content
KitploitKITPLOIT
ツールエクスプロイトブログ
Log in
提出
ツールエクスプロイトブログ
提出

ハッキング、侵入テスト、サイバーセキュリティツールをあなたのセキュリティアーセナルに!

Kitploitはハッキング、サイバーセキュリティ、ペネトレーションテストのツールディレクトリです。最新のプロジェクトアップデートを見つけて、脆弱性の発見、システム分析、テストの自動化、セキュリティの強化を行いましょう。

フィードお問い合わせプライバシー© 2026 Kitploit

ツールディレクトリ

カテゴリ

すべてのカテゴリを見る
Loading categories
ツール/GitHubGitHub/alexbiller/salesforce-cve-remediation-demo
Vulnerability AnalysisCode AnalysisWeb SecurityLearning & Education
GitHubalexbiller/salesforce-cve-remediation-demo

salesforce-cve-remediation-demo

Unofficial demo built with Devin - synthetic data: CVE-2026-117561 command-injection remediation walkthrough

リポジトリを見る
18日前未レビュー
共有
要求された言語のコンテンツは利用できません。英語版を表示しています。

CVE-2026-117561 remediation demo for Salesforce (unofficial)

Unofficial demo built with Devin - synthetic data. Not affiliated with, endorsed by, or connected to Salesforce. The orgops-bridge service, people, tickets and commit IDs are fictional. No real customer data, credentials or Salesforce systems are used.

This static web app shows Devin working a published security issue end to end. The issue is CVE-2026-117561 (published 2026-10-27): OS command injection in Codefriar sf-mcp through 1.3.2, a community MCP server that drives the Salesforce CLI. Its escapeValue() does not neutralize backticks, $() and other shell metacharacters, so crafted sf flag values reach execSync and run as shell commands.

To show the same class of flaw, this repo contains a small synthetic Python service, orgops-bridge. It lets an AI assistant run sf commands for org admins and has the same bug. The repo also includes real regression tests, Devin's fix, and fixes for every other instance of the pattern in the sample.

Live demo: https://htmlpreview.github.io/?https://github.com/AlexBiller/salesforce-cve-remediation-demo/blob/main/index.html

Main screen

Walkthrough (under 5 minutes)

  1. Advisory summary. A plain-language explanation of the issue and the affected code pattern, with the vulnerable lines highlighted. You can type a flag value and see the command string the shell would receive. Nothing is executed.
  2. Run regression test. Runs test_cli_injection.py against sample/vulnerable and streams the output: 4 of 5 tests fail.
  3. Apply Devin's fix. Shows the diff (argv list, shell=False, allowlisted commands and flag names) and re-runs the tests: 5 of 5 pass.
  4. Other instances. Covers 4 more vulnerable call sites (export.py, apex_logs.py, deploy.py, sandbox.py) and 1 call site that was reviewed and is already safe (org_info.py). Each comes with its diff, before/after test results, and an Approve change button.
  5. Export report. Download a remediation report for the security team as Markdown or JSON, or copy it to the clipboard.

Progress is saved in localStorage. Reset demo in the header restores the seeded state. The demo has no login, no backend, and no third-party services.

Run locally

python3 seed/seed.py          # runs the sample tests and regenerates data/seed.json + data/seed.js (deterministic)
python3 -m http.server 8000   # any static file server works
# open http://localhost:8000

Run the sample regression tests yourself. They use only the Python 3.10+ standard library:

cd sample/tests
ORGOPS_IMPL=vulnerable python3 -m unittest -v   # 9 failures: injection succeeds
ORGOPS_IMPL=fixed      python3 -m unittest -v   # all 12 pass

The tests are safe to run. sf is replaced by tests/fake_sf.py, which records its argv and never contacts an org. Each attack payload only does touch <tempdir>/canary, and a test fails if that file appears.

Project layout

PathPurpose
sample/vulnerable/orgops/Synthetic service with the flaw (cli.py is the primary instance, plus 4 variants and 1 safe module).
sample/fixed/orgops/The same service after Devin's fix, including the shared no-shell helper _sf.py.
sample/tests/Regression tests (test_cli_injection.py, test_other_sinks.py), fixtures, and the fake sf binary.
seed/seed.pySeed script. Runs the tests against both copies, computes diffs with difflib, and adds fictional review metadata from a seeded RNG.
data/seed.json, data/seed.jsGenerated data. Both are checked in so the site works on any static host, or from file://, with no build step.
index.html, app.js, styles.cssDependency-free single-page app with hash routes #/summary, #/test, #/fix, #/instances and #/report.

Deployment

The site is fully static with no build step, so any static host works.

  • Current public URL: htmlpreview.github.io renders the files on the main branch directly.
  • GitHub Pages (optional): in Settings → Pages, choose Deploy from a branch and select main / (root). The site is then served at https://alexbiller.github.io/salesforce-cve-remediation-demo/.

Data and credentials

  • All data is synthetic and comes from seed/seed.py and the sample code in sample/.
  • No credentials are needed or included. The demo has no login.
  • The only real-world reference is the public NVD advisory, linked for background.
ツールをダウンロード

人気

すべて見る →

コミュニティで最も使われているツールを見つけましょう。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 究極のOSINTツールキット:調査グラフ、信頼度スコアリング、エイリアスファミリー、マップ、タイムライン、レポート。49個のモジュール、400以上のサイト、APIキー不要。

    1.1k
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock ワンタップ実行アプリ(CVE-2026-43499)

    618
  • 3

    looking-glass

    anonghosty/looking-glass

    ShadowserverレポートをMongoDBに取り込み、インタラクティブなマップ、分析、調査結果、アドバイザリ、エグゼクティブダッシュボードとして再生するCSIRTプラットフォーム。

    407
  • 4

    ARTEX

    baarai/artex

    プランナー/ワーカーエージェント、資産グラフと探索グラフ、MITMトラフィック記録、脆弱性の再テストを備えたLLMマルチエージェント自律ペネトレーションテストプラットフォーム。

    324
  • 5

    jumpserver

    jumpserver/jumpserver

    JumpServerは、オープンソースの特権アクセス管理(PAM)プラットフォームであり、DevOps および IT チームに対し、Webブラウザを介してSSH、RDP、Kubernetes、データベース、RemoteAppエンドポイントへのオンデマンドで安全なアクセスを提供します。

    279
  • 6

    Aliens_eye

    arxhr007/aliens_eye

    ウェブ全体で7,700以上のソーシャルメディア上の身元を発見・マッピングするAI搭載OSINTエンジン

    270

すべてのツールを探索

ツールコレクションを閲覧

すべてのツールを見る →