How severe is GHSA-68qx-whxm-h4c4?

GHSA-68qx-whxm-h4c4 has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-68qx-whxm-h4c4?

GHSA-68qx-whxm-h4c4 affects the following packages: com.tinfoilsecurity.plugins:tinfoil-scan (Maven). Ecosystems affected: Maven.

How do I fix GHSA-68qx-whxm-h4c4?

Update com.tinfoilsecurity.plugins:tinfoil-scan to 2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68qx-whxm-h4c4 is resolved across your whole dependency graph.

How do I detect GHSA-68qx-whxm-h4c4 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.tinfoilsecurity.plugins:tinfoil-scan. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-68qx-whxm-h4c4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-68qx-whxm-h4c4?

O3 pinpoints whether GHSA-68qx-whxm-h4c4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-68qx-whxm-h4c4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-68qx-whxm-h4c4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-68qx-whxm-h4c4?

GHSA-68qx-whxm-h4c4 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-68qx-whxm-h4c4 published, and has it been updated?

GHSA-68qx-whxm-h4c4 was published on May 14, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

GHSA-68qx-whxm-h4c4

MEDIUMFix: jenkinsci/tinfoil-scan-plugin@26b3944

GHSA-68qx-whxm-h4c4 is a medium-severity (CVSS 5.5) Information Exposure vulnerability in com.tinfoilsecurity.plugins:tinfoil-scan. O3 Security confirms whether GHSA-68qx-whxm-h4c4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Exposure of sensitive information vulnerability

Also known asCVE-2018-1999041

Published

May 14, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 16, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.tinfoilsecurity.plugins:tinfoil-scan

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An exposure of sensitive information vulnerability exists in Jenkins Tinfoil Security Plugin 1.6.1 and earlier in TinfoilScanRecorder.java that allows attackers with file system access to the Jenkins master to obtain the API secret key stored in this plugin's configuration.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.tinfoilsecurity.plugins:tinfoil-scan`	all versions	2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.tinfoilsecurity.plugins:tinfoil-scan. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.tinfoilsecurity.plugins:tinfoil-scan to 2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-68qx-whxm-h4c4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-68qx-whxm-h4c4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-68qx-whxm-h4c4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-68qx-whxm-h4c4 in your dependencies?

O3 detects GHSA-68qx-whxm-h4c4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works