# CVE-2023-45196: Adminer and AdminerEvo denial of service via HTTP redirect


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/AU:Y`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 24 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** DEBIAN-CVE-2023-45196, GHSA-2fjv-ffr6-wh68, UBUNTU-CVE-2023-45196

## What is CVE-2023-45196?

CVE-2023-45196 is a medium-severity vulnerability in Adminer, published on 24 Jun 2024. 

### Official description

Adminer and AdminerEvo allow an unauthenticated remote attacker to cause a denial of service by connecting to an attacker-controlled service that responds with HTTP redirects. The denial of service is subject to PHP configuration limits. Adminer is no longer supported, but this issue was fixed in AdminerEvo version 4.8.4.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2023-45196?

It affects 1 product.


Products: Adminerevo Adminerevo.

## How do I fix CVE-2023-45196?

Upgrade to a fixed version.

## Is CVE-2023-45196 being exploited?

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

## Other vulnerabilities in Adminer

- [CVE-2023-45197](https://insights.sbomify.com/CVE-2023-45197/): Adminer and AdminerEvo vulnerable to directory traversal and file upload (critical 9.2)
- [CVE-2023-45195](https://insights.sbomify.com/CVE-2023-45195/): Adminer and AdminerEvo SSRF (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45196 and fix it if it is affected.

What it is: CVE-2023-45196 is a medium-severity vulnerability in Adminer, published on 24 Jun 2024. 
Exploitation: There is no known exploitation of CVE-2023-45196 in the wild and no public exploit code.

Affected product: Adminer. 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-2023-45196/ (Markdown: https://insights.sbomify.com/CVE-2023-45196/index.md)
```

## Sources

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

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