Vulnerability-Lookup

PYSEC-2026-339

Vulnerability from pysec - Published: 2026-06-29 11:50 - Updated: 2026-07-01 20:22

Details

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 — CreateJiraBotView - src/firefighter/raid/serializers.py — LandbotIssueRequestSerializer.attachments - src/firefighter/raid/client.py — RaidJiraClient.add_attachments_to_issue

### Patches Fixed in firefighter-incident 0.0.54: - CreateJiraBotView now enforces BearerTokenAuthentication + IsAuthenticated. - attachments URLs 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_bot to trusted networks only (VPN, internal load balancer). - Rotate or revoke the Jira API token configured as RAID_JIRA_API_PASSWORD; this breaks jira.create_issue() before the vulnerable attachment fetch is reached (legitimate traffic is also blocked — emergency mitigation only). - Enforce IMDSv2 with HttpPutResponseHopLimit=1 on 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

Severity

9.9 (Critical)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L

Impacted products

Name	purl
firefighter-incident	pkg:pypi/firefighter-incident

Aliases

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "firefighter-incident",
        "purl": "pkg:pypi/firefighter-incident"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.54"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.0.1",
        "0.0.10",
        "0.0.11",
        "0.0.12",
        "0.0.13",
        "0.0.14",
        "0.0.15",
        "0.0.16",
        "0.0.17",
        "0.0.18",
        "0.0.19",
        "0.0.1rc1",
        "0.0.1rc2",
        "0.0.2",
        "0.0.20",
        "0.0.21",
        "0.0.22",
        "0.0.23",
        "0.0.24",
        "0.0.25",
        "0.0.26",
        "0.0.27",
        "0.0.28",
        "0.0.29",
        "0.0.3",
        "0.0.30",
        "0.0.31",
        "0.0.32",
        "0.0.33",
        "0.0.34",
        "0.0.35",
        "0.0.36",
        "0.0.37",
        "0.0.38",
        "0.0.39",
        "0.0.4",
        "0.0.40",
        "0.0.41",
        "0.0.42",
        "0.0.43",
        "0.0.44",
        "0.0.45",
        "0.0.46",
        "0.0.47",
        "0.0.48",
        "0.0.49",
        "0.0.5",
        "0.0.50",
        "0.0.51",
        "0.0.52",
        "0.0.53",
        "0.0.6",
        "0.0.7",
        "0.0.8",
        "0.0.9"
      ]
    }
  ],
  "aliases": [
    "CVE-2026-42864",
    "GHSA-fqvv-jvhr-g5jc"
  ],
  "details": "### Impact\n  The `POST /api/v2/firefighter/raid/jira_bot` endpoint (`CreateJiraBotView`) is\n  reachable without authentication (`permission_classes = [permissions.AllowAny]`).\n  Its `attachments` payload is fetched server-side via `httpx.get()` with no URL\n  validation, then uploaded as an attachment on the Jira ticket that gets created.\n\n  An unauthenticated caller able to reach the ingress can coerce the pod into\n  fetching arbitrary URLs \u2014 including the cloud metadata endpoint at\n  `http://169.254.169.254/` \u2014 and exfiltrate the response as a Jira attachment.\n\n  On EC2/EKS deployments that do not enforce IMDSv2, this allows theft of the\n  temporary AWS credentials attached to the pod\u0027s IAM role. The docstring on the\n  view claims a Bearer token is required, but the code does not enforce it.\n\n  Affected code paths:\n  - `src/firefighter/raid/views/__init__.py` \u2014 `CreateJiraBotView`\n  - `src/firefighter/raid/serializers.py` \u2014 `LandbotIssueRequestSerializer.attachments`\n  - `src/firefighter/raid/client.py` \u2014 `RaidJiraClient.add_attachments_to_issue`\n\n  ### Patches\n  Fixed in `firefighter-incident` `0.0.54`:\n  - `CreateJiraBotView` now enforces `BearerTokenAuthentication` + `IsAuthenticated`.\n  - `attachments` URLs are validated: http(s) scheme only, max 10 URLs, rejection\n    of any host resolving to a private, loopback, link-local, reserved, multicast\n    or unspecified IP (IPv4 and IPv6).\n  - Fixes an unrelated `KeyError(\u0027attachments\u0027)` surfaced during regression testing.\n\n  Users should upgrade to `0.0.54` or later.\n\n  ### Workarounds\n  Until upgrade is possible, any one of the following blocks end-to-end exploitation:\n  - Restrict ingress access to `/api/v2/firefighter/raid/jira_bot` to trusted\n    networks only (VPN, internal load balancer).\n  - Rotate or revoke the Jira API token configured as `RAID_JIRA_API_PASSWORD`;\n    this breaks `jira.create_issue()` before the vulnerable attachment fetch is\n    reached (legitimate traffic is also blocked \u2014 emergency mitigation only).\n  - Enforce IMDSv2 with `HttpPutResponseHopLimit=1` on EC2/EKS nodes. This does\n    not fix the SSRF itself but neutralises the IAM-credential-theft path.\n\n  ### Resources\n  - CWE-918: Server-Side Request Forgery\n  - CWE-306: Missing Authentication for Critical Function",
  "id": "PYSEC-2026-339",
  "modified": "2026-07-01T20:22:52.903088Z",
  "published": "2026-06-29T11:50:50.634046Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ManoManoTech/firefighter-incident/security/advisories/GHSA-fqvv-jvhr-g5jc"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42864"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ManoManoTech/firefighter-incident/commit/2586679e6f32c12d223668b73e98f4c4de7b771f"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ManoManoTech/firefighter-incident"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/firefighter-incident"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-fqvv-jvhr-g5jc"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft"
}

CVE-2026-42864 (GCVE-0-2026-42864)

Vulnerability from cvelistv5 – Published: 2026-05-11 18:19 – Updated: 2026-05-11 19:34

Title

FireFighter: Unauthenticated SSRF in Raid jira_bot endpoint allows IAM credential theft

Summary

FireFighter is an incident management application. Prior to 0.0.54, 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 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. This vulnerability is fixed in 0.0.54.

Severity

9.9 (Critical)


                        
                          CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L

SSVC

Exploitation: none Automatable: yes Technical Impact: partial

CISA Coordinator · CISA-ADP (v2.0.3)

Decision recorded 2026-05-11 19:34 UTC

CWE

CWE-306 - Missing Authentication for Critical Function
CWE-918 - Server-Side Request Forgery (SSRF)

Assigner

GitHub_M CNA under the mitre root

CNA scorecard C 72/100 over 8035 records in the last 180 days details

References

1 reference

URL	Tags
https://github.com/ManoManoTech/firefighter-incid…	x_refsource_CONFIRM

Impacted products

1 product

Vendor	Product	Version
ManoManoTech	firefighter-incident	Affected: < 0.0.54

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-42864",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-05-11T19:34:04.380041Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-05-11T19:34:12.513Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "firefighter-incident",
          "vendor": "ManoManoTech",
          "versions": [
            {
              "status": "affected",
              "version": "\u003c 0.0.54"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "FireFighter is an incident management application. Prior to 0.0.54, 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 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\u0027s IAM role. The docstring on the view claims a Bearer token is required, but the code does not enforce it. This vulnerability is fixed in 0.0.54."
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "LOW",
            "baseScore": 9.9,
            "baseSeverity": "CRITICAL",
            "confidentialityImpact": "HIGH",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L",
            "version": "3.1"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-306",
              "description": "CWE-306: Missing Authentication for Critical Function",
              "lang": "en",
              "type": "CWE"
            }
          ]
        },
        {
          "descriptions": [
            {
              "cweId": "CWE-918",
              "description": "CWE-918: Server-Side Request Forgery (SSRF)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T18:19:13.416Z",
        "orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
        "shortName": "GitHub_M"
      },
      "references": [
        {
          "name": "https://github.com/ManoManoTech/firefighter-incident/security/advisories/GHSA-fqvv-jvhr-g5jc",
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/ManoManoTech/firefighter-incident/security/advisories/GHSA-fqvv-jvhr-g5jc"
        }
      ],
      "source": {
        "advisory": "GHSA-fqvv-jvhr-g5jc",
        "discovery": "UNKNOWN"
      },
      "title": "FireFighter: Unauthenticated SSRF in Raid jira_bot endpoint allows IAM credential theft"
    }
  },
  "cveMetadata": {
    "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
    "assignerShortName": "GitHub_M",
    "cveId": "CVE-2026-42864",
    "datePublished": "2026-05-11T18:19:13.416Z",
    "dateReserved": "2026-04-30T16:44:48.380Z",
    "dateUpdated": "2026-05-11T19:34:12.513Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2"
}

GHSA-FQVV-JVHR-G5JC

Vulnerability from github – Published: 2026-05-05 18:21 – Updated: 2026-10-27 16:41

Summary

FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft

Details

Impact

Users should upgrade to 0.0.54 or later.

### Resources - CWE-918: Server-Side Request Forgery - CWE-306: Missing Authentication for Critical Function

Severity

9.9 (Critical)


                  
                    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L

Show details on source website

JSON

To clipboard

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "firefighter-incident"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.0.54"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-42864"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-306",
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-05T18:21:17Z",
    "nvd_published_at": "2026-05-11T19:16:24Z",
    "severity": "CRITICAL"
  },
  "details": "### Impact\n  The `POST /api/v2/firefighter/raid/jira_bot` endpoint (`CreateJiraBotView`) is\n  reachable without authentication (`permission_classes = [permissions.AllowAny]`).\n  Its `attachments` payload is fetched server-side via `httpx.get()` with no URL\n  validation, then uploaded as an attachment on the Jira ticket that gets created.\n\n  An unauthenticated caller able to reach the ingress can coerce the pod into\n  fetching arbitrary URLs \u2014 including the cloud metadata endpoint at\n  `http://169.254.169.254/` \u2014 and exfiltrate the response as a Jira attachment.\n\n  On EC2/EKS deployments that do not enforce IMDSv2, this allows theft of the\n  temporary AWS credentials attached to the pod\u0027s IAM role. The docstring on the\n  view claims a Bearer token is required, but the code does not enforce it.\n\n  Affected code paths:\n  - `src/firefighter/raid/views/__init__.py` \u2014 `CreateJiraBotView`\n  - `src/firefighter/raid/serializers.py` \u2014 `LandbotIssueRequestSerializer.attachments`\n  - `src/firefighter/raid/client.py` \u2014 `RaidJiraClient.add_attachments_to_issue`\n\n  ### Patches\n  Fixed in `firefighter-incident` `0.0.54`:\n  - `CreateJiraBotView` now enforces `BearerTokenAuthentication` + `IsAuthenticated`.\n  - `attachments` URLs are validated: http(s) scheme only, max 10 URLs, rejection\n    of any host resolving to a private, loopback, link-local, reserved, multicast\n    or unspecified IP (IPv4 and IPv6).\n  - Fixes an unrelated `KeyError(\u0027attachments\u0027)` surfaced during regression testing.\n\n  Users should upgrade to `0.0.54` or later.\n\n  ### Workarounds\n  Until upgrade is possible, any one of the following blocks end-to-end exploitation:\n  - Restrict ingress access to `/api/v2/firefighter/raid/jira_bot` to trusted\n    networks only (VPN, internal load balancer).\n  - Rotate or revoke the Jira API token configured as `RAID_JIRA_API_PASSWORD`;\n    this breaks `jira.create_issue()` before the vulnerable attachment fetch is\n    reached (legitimate traffic is also blocked \u2014 emergency mitigation only).\n  - Enforce IMDSv2 with `HttpPutResponseHopLimit=1` on EC2/EKS nodes. This does\n    not fix the SSRF itself but neutralises the IAM-credential-theft path.\n\n  ### Resources\n  - CWE-918: Server-Side Request Forgery\n  - CWE-306: Missing Authentication for Critical Function",
  "id": "GHSA-fqvv-jvhr-g5jc",
  "modified": "2026-10-27T16:41:07Z",
  "published": "2026-05-05T18:21:17Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ManoManoTech/firefighter-incident/security/advisories/GHSA-fqvv-jvhr-g5jc"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42864"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ManoManoTech/firefighter-incident/commit/2586679e6f32c12d223668b73e98f4c4de7b771f"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ManoManoTech/firefighter-incident"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pypa/advisory-database/tree/main/vulns/firefighter-incident/PYSEC-2026-339.yaml"
    },
    {
      "type": "WEB",
      "url": "https://pypi.org/project/firefighter-incident"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "FireFighter has unauthenticated SSRF in its Raid jira_bot endpoint that allows IAM credential theft"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

Order JSON

How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Publication & reservation Sightings KEV catalogs Other timestamps

Loading timeline…

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

PYSEC-2026-339

Impact

CVE-2026-42864 (GCVE-0-2026-42864)

GHSA-FQVV-JVHR-G5JC

Impact

Tags

Sightings

Nomenclature

Vulnerability timeline

Related by attack behaviour