Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/xiaoqimikko/scc-check
Static AnalysisVulnerability ScannersVulnerability AnalysisDevSecOpsSupply Chain Security
GitHubxiaoqimikko/scc-check

scc-check

Offline checker for Spring Cloud Config CVE-2026-40982 — tells you whether your version line has an OSS fix at all (3.1.x/4.1.x/4.2.x: it does not)

View Repository
122 months agoNot yet reviewed
Share

scc-check

Spring Cloud Config CVE-2026-40982 offline troubleshooting tool — zero dependencies, single jar, no network access.

It doesn't answer "am I affected?" — it answers the more painful question:

On my version line, is there actually a secure version on Maven Central that I can upgrade to?

For the three lines 3.1.x / 4.1.x / 4.2.x, the answer is no.


Why it's needed

官方 advisory(spring.io/security/cve-2026-40982)给出的修复版:

版本线官方修复版可得性Maven Central 上该线最高版你能升上去吗
3.1.x3.1.14Enterprise Support Only3.1.10❌
4.1.x4.1.10Enterprise Support Only4.1.7❌
4.2.x4.2.7Enterprise Support Only4.2.4❌
4.3.x4.3.3OSS4.3.4✅
5.0.x5.0.3OSS5.0.4✅

Those three fixed versions are not in public repositories. Anyone can verify:

curl -sI https://repo1.maven.org/maven2/org/springframework/cloud/spring-cloud-config-server/4.2.7/
# HTTP/1.1 404 Not Found

And automated tools won't tell you this — in the structured data of the GitHub advisory, the first_patched_version for these three lines is simply null:

{"range": "<= 3.1.13",          "first_patched_version": null}
{"range": ">= 4.1.0, <= 4.1.9", "first_patched_version": null}
{"range": ">= 4.2.0, <= 4.2.6", "first_patched_version": null}
{"range": ">= 4.3.0, <= 4.3.2", "first_patched_version": "4.3.3"}
{"range": ">= 5.0.0, <= 5.0.2", "first_patched_version": "5.0.3"}

Dependabot / OSV consume exactly this data. Without an upgrade target, no upgrade recommendation can be given.


Usage

java -jar scc-check.jar <目录或 jar/war 路径>

# 中文乱码时(Windows 控制台代码页与 Java 判断常常对不上):
java -jar scc-check.jar target/ --utf8

需要 Java 17+。运行时零依赖,可直接丢进离线环境。

退出码:2 有版本线升不上去 · 1 受影响但可升 / 判不了 · 0 未发现 · 3 用法或路径错

它查哪些地方

  • .jar / .war 文件名
  • Spring Boot fat jar 与 war 的内嵌依赖(BOOT-INF/lib/、WEB-INF/lib/)
  • jar 内 Maven 元数据(META-INF/maven/.../pom.properties)—— jar 被改名也认得出
  • pom.xml

三件它刻意不做的事

1. 不把客户端算成受影响。 本 CVE 只影响服务端 spring-cloud-config-server。引了 spring-cloud-starter-config (客户端)的项目不受影响,工具会明确告诉你,而不是让你白紧张。

2. 不对 4.0.x 下判定。 官方 advisory 的任何区间都没有覆盖 4.0.x(4.0.0 > 3.1.13,不落在无下界那条里)。 工具只报「不在官方覆盖范围内」,不报 CRITICAL —— 靠推测填判定表会让人做错决定。

3. 读不出版本时明说「判不了」,绝不当成安全。 Spring Cloud 用 release train 统一管版本,pom.xml 里常常根本没有 <version>。 这种情况工具会告诉你去扫构建产物,而不是假装没找到问题。 同样,scope 为 test / provided 的依赖不传递给使用者,不算暴露面; 被 XML 注释包住的依赖会被剥掉。


判定表是生成的,不是手抄的

tools/gen_rules.py 从两个一手数据源编译出 RuleTable.java:

  • GitHub advisory GHSA-6g23-24mc-hx6x → 受影响区间 + 官方修复版
  • repo1.maven.org 的 maven-metadata.xml → 公开仓库里实际存在的版本

并带四条断言:区间数 ≥5、first_patched=null 的 ≥3、版本线 ≥5、判为 ENTERPRISE_ONLY 的 ≥3。任何一条不满足就直接中止,不生成文件 —— 否则解析一失败就会产出一张空表,而单元测试对着空表照样全绿。

python tools/gen_rules.py     # 重新生成判定表
mvn test                      # 31 个测试

Disclaimer

This tool only performs version comparison. It does not check whether your Config Server is actually exposed to the public internet, whether it has a WAF, or whether it has been mitigated by other means. The results are a starting point for investigation, not a security conclusion. Refer to the official advisory.

License

MIT


Need a deeper investigation?

This tool answers "am I affected or not". The following questions it cannot answer, but I can help with:

  • Dependencies have been shaded / relocated, or the build artifacts simply cannot be obtained
  • What needs to be determined is whether "this CVE will actually trigger on our call chain", not just a version match
  • Customization is needed for your own build process or internal network environment, or integration into an existing pipeline
  • You are dealing with a similar issue in another component and there is no ready-made tool yet

📮 [email protected] — Describe the situation, and within 24 hours I will give you a one-page written reply: whether it can be done, where the difficulty lies, and roughly how long it will take. This step is free, and you don't need to commit to anything first.

Exit codes

CodeMeaning
0Scan completed, and every file was actually read, with no findings requiring action
4Some file could not be read — not a zip, truncated content, or read failure

🔴 4 was added on 2026-09-09, and the reason for adding it is worth explaining clearly. Before that, unreadable files only left a single line of notice in the output, while the exit code remained 0 — the trace was for humans to see, but CI and scripts look at the exit code, so "I couldn't read it" meant "passed" in automation. A corrupted, encrypted, or incompletely downloaded jar would quietly turn into "no issues found".

"I can't read it" and "you are safe" must be two different statements.

⚠️ A legitimate empty jar does not count as unreadable (a 22-byte EOCD record is a real empty zip), and will not trigger 4 — when there are too many false alarms, no one pays attention to the real ones.

For the meaning of the other exit codes, see the judgment tiers and usage instructions above.

Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    772
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    505
  • 3

    ARTEX

    baarai/artex

    LLM multi-agent autonomous penetration testing platform with planner/worker agents, asset and exploration graphs, MITM traffic recording, and vulnerability retesting.

    420
  • 4

    redforge

    cybersecurity91/redforge

    Browser-side red team toolkit with 102 offline tools for recon, payload generation, credential attacks, crypto, encoding and engagement reporting.

    345
  • 5

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    The system of action for AI-native cybersecurity—where intent becomes governed execution, evidence becomes operational memory, and every operation improves the next.

    260
  • 6

    antifox

    antifox-ai/antifox

    AI multi-agent autonomous penetration testing platform that runs recon, attack-surface discovery, exploitation validation and evidence-backed report delivery.

    251

Explore all tools

Browse our collection of tools

View all tools →