# CVE-2024-9410: Ada.cx SSRF via Sentry Misconfiguration

> Attackers can perform blind server-side request forgeries via a data scraping endpoint due to Sentry misconfiguration in Ada.cx.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2024
- **Updated:** 4 Oct 2024
- **Also known as:** GHSA-vhp6-hrqq-rpqj

## What is CVE-2024-9410?

CVE-2024-9410 is a medium-severity server-side request forgery vulnerability in Ada.cx Sentry Component, published on 4 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ada.cx's Sentry configuration allowed for blind server-side request forgeries (SSRF) through the use of a data scraping endpoint.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-9410?

It affects 1 product.


Products: Ada Ada.

## How do I fix CVE-2024-9410?

No fix has been published for CVE-2024-9410 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-9410 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9410 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-9410 and fix it if it is affected.

What it is: CVE-2024-9410 is a medium-severity server-side request forgery vulnerability in Ada.cx Sentry Component, published on 4 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-9410 exists.

Affected product: Ada.cx Sentry Component. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-9410/ (Markdown: https://insights.sbomify.com/CVE-2024-9410/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-9410
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-9410
- OSV: https://osv.dev/vulnerability/CVE-2024-9410

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-9410/
Summaries are generated and may contain mistakes; the official description above is the record.