# CVE-2022-45930: SQL injection in n/a

> SQL injection in OpenDaylight AAA allows attackers to read or modify domain data via the deleteDomain function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 27 Nov 2022
- **Updated:** 29 Apr 2025
- **Also known as:** GHSA-5chc-59gh-mmpx

## What is CVE-2022-45930?

CVE-2022-45930 is a high-severity SQL injection vulnerability in n/a, published on 27 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL injection issue was discovered in AAA in OpenDaylight (ODL) before 0.16.5. The aaa-idm-store-h2/src/main/java/org/opendaylight/aaa/datastore/h2/DomainStore.java deleteDomain function is affected for the /auth/v1/domains/ API interface.

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

## Which versions are affected by CVE-2022-45930?

It affects 1 product.


Products: Linuxfoundation Opendaylight.

## How do I fix CVE-2022-45930?

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

## Is CVE-2022-45930 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45931](https://insights.sbomify.com/CVE-2022-45931/): SQL injection in n/a (high 7.5)
- [CVE-2022-45932](https://insights.sbomify.com/CVE-2022-45932/): SQL injection in n/a (high 7.5)
- [CVE-2015-1857](https://insights.sbomify.com/CVE-2015-1857/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-45930 and fix it if it is affected.

What it is: CVE-2022-45930 is a high-severity SQL injection vulnerability in n/a, published on 27 Nov 2022. 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-2022-45930 exists.

Affected product: n/a. 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-2022-45930/ (Markdown: https://insights.sbomify.com/CVE-2022-45930/index.md)
```

## Sources

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

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