CVE-2024-43379 is a low-severity (CVSS 3.4) Server-Side Request Forgery (SSRF) vulnerability in github.com/trufflesecurity/trufflehog/v3. A fix is available for github.com/trufflesecurity/trufflehog/v3 — see the affected versions and patch details below.
TruffleHog has a Blind SSRF in some Detectors
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-43379.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/trufflesecurity/trufflehog/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
What kind of vulnerability is it? Who is impacted?
This vulnerability allows a malicious actor to craft data in a way that, when scanned by specific detectors, could trigger the detector to make an unauthorized request to an endpoint chosen by the attacker. For an exploit to be effective, the target endpoint must be an unauthenticated GET endpoint that produces side effects. The victim must scan the maliciously crafted data and have such an endpoint targeted for the exploit to succeed.
Patches
Has the problem been patched? What versions should users upgrade to?
The vulnerability has been resolved in TruffleHog v3.81.9 and later versions. Users should upgrade to this or a more recent version to mitigate the issue.
Special thanks to Karan Bamal, Security Researcher at Sentinel One for this discovery
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/trufflesecurity/trufflehog/v3 | all versions | 3.81.9go get github.com/trufflesecurity/trufflehog/v3@v3.81.9 |
Affected Products
trufflehogtrufflesecurityDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/trufflesecurity/trufflehog/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/trufflesecurity/trufflehog/v3 to 3.81.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-43379 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.
Frequently Asked Questions
Is CVE-2024-43379 in your dependencies?
Find it across Go, including transitive dependencies.