GHSA-fqvv-jvhr-g5jc is a critical-severity (CVSS 9.9) Missing Authentication vulnerability in firefighter-incident. A fix is available for firefighter-incident — see the affected versions and patch details below.
FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-fqvv-jvhr-g5jc plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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.54pip install --upgrade 'firefighter-incident==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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fqvv-jvhr-g5jc can be triaged on real exposure rather than presence alone.
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 Security finds GHSA-fqvv-jvhr-g5jc across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.