# CVE-2024-1839: SQL injection in 911 Emergency Gateway (EGW)

> Unauthenticated remote attackers can exploit SQL injection in the login form to execute code, exfiltrate data, or manipulate the database.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:L/S:P/AU:Y/R:U/V:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-43wj-hwhg-9h4m

## What is CVE-2024-1839?

CVE-2024-1839 is a critical SQL injection vulnerability in Intrado 911 Emergency Gateway (EGW), published on 26 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Intrado 911 Emergency Gateway login form is vulnerable to an unauthenticated blind time-based SQL injection, which may allow an unauthenticated remote attacker to execute malicious code, exfiltrate data, or manipulate the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

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

It affects 1 product.


Products: Intrado 911 Emergency Gateway Firmware.

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

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

## Is CVE-2024-1839 being exploited?

There is no known exploitation of CVE-2024-1839 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1839 is a critical SQL injection vulnerability in Intrado 911 Emergency Gateway (EGW), published on 26 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1839 in the wild and no public exploit code.

Affected product: Intrado 911 Emergency Gateway (EGW). 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-1839/ (Markdown: https://insights.sbomify.com/CVE-2024-1839/index.md)
```

## Sources

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

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