GHSA-fqvv-jvhr-g5jc
CRITICALGHSA-fqvv-jvhr-g5jc is a critical-severity (CVSS 9.9) vulnerability in firefighter-incident. O3 Security confirms whether GHSA-fqvv-jvhr-g5jc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft
Blast Radius
firefighter-incidentReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Impact
The POST /api/v2/firefighter/raid/jira_bot endpoint (CreateJiraBotView) is
reachable without authentication (permission_classes = [permissions.AllowAny]).
Its attachments payload is fetched server-side via httpx.get() with no URL
validation, then uploaded as an attachment on the Jira ticket that gets created.
An unauthenticated caller able to reach the ingress can coerce the pod into
fetching arbitrary URLs — including the cloud metadata endpoint at
http://169.254.169.254/ — and exfiltrate the response as a Jira attachment.
On EC2/EKS deployments that do not enforce IMDSv2, this allows theft of the temporary AWS credentials attached to the pod's IAM role. The docstring on the view claims a Bearer token is required, but the code does not enforce it.
Affected code paths:
src/firefighter/raid/views/__init__.py—CreateJiraBotViewsrc/firefighter/raid/serializers.py—LandbotIssueRequestSerializer.attachmentssrc/firefighter/raid/client.py—RaidJiraClient.add_attachments_to_issue
Patches
Fixed in firefighter-incident 0.0.54:
CreateJiraBotViewnow enforcesBearerTokenAuthentication+IsAuthenticated.attachmentsURLs are validated: http(s) scheme only, max 10 URLs, rejection of any host resolving to a private, loopback, link-local, reserved, multicast or unspecified IP (IPv4 and IPv6).- Fixes an unrelated
KeyError('attachments')surfaced during regression testing.
Users should upgrade to 0.0.54 or later.
Workarounds
Until upgrade is possible, any one of the following blocks end-to-end exploitation:
- Restrict ingress access to
/api/v2/firefighter/raid/jira_botto trusted networks only (VPN, internal load balancer). - Rotate or revoke the Jira API token configured as
RAID_JIRA_API_PASSWORD; this breaksjira.create_issue()before the vulnerable attachment fetch is reached (legitimate traffic is also blocked — emergency mitigation only). - Enforce IMDSv2 with
HttpPutResponseHopLimit=1on EC2/EKS nodes. This does not fix the SSRF itself but neutralises the IAM-credential-theft path.
Resources
- CWE-918: Server-Side Request Forgery
- CWE-306: Missing Authentication for Critical Function
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | firefighter-incident | all versions | 0.0.54 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for firefighter-incident. 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 firefighter-incident to 0.0.54 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fqvv-jvhr-g5jc 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-fqvv-jvhr-g5jc 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-fqvv-jvhr-g5jc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fqvv-jvhr-g5jc in your dependencies?
O3 detects GHSA-fqvv-jvhr-g5jc across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.