# CVE-2020-13945: Hardcoded credentials in Apache APISIX

> Attackers can access APISIX management data using the default token if IP restrictions are removed, requiring configuration changes to secure the Admin API.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-apisix-2020-13945, GHSA-c538-784j-qcxc

## What is CVE-2020-13945?

CVE-2020-13945 is a medium-severity vulnerability in Apache APISIX, published on 7 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Apache APISIX, the user enabled the Admin API and deleted the Admin API access IP restriction rules. Eventually, the default token is allowed to access APISIX management data. This affects versions 1.2, 1.3, 1.4, 1.5.

## Which versions are affected by CVE-2020-13945?

1 open source package ship an affected version, including apisix. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apisix` | Bitnami | From 1.2.0 | 1.5.1 |

Products: Apache Apisix.

## How do I fix CVE-2020-13945?

Upgrade apisix to 1.5.1 or later.

## Is CVE-2020-13945 being exploited?

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

Public exploit code:

- Apisix系列漏洞：未授权漏洞（CVE-2021-45232）、默认秘钥（CVE-2020-13945）批量探测。 (github_poc): https://github.com/YutuSec/Apisix_Crack
- APISIX Admin API default access token RCE (metasploit)
- Vulhub apisix/CVE-2020-13945: Apache APISIX Default Admin Token RCE (CVE-2020-13945), run with Isoloom (github_poc): https://github.com/CyberCTF/vulhub-apisix-cve-2020-13945
- Apache APISIX - Insufficiently Protected Credentials (nuclei): http/cves/2020/CVE-2020-13945.yaml

## Other vulnerabilities in Apache APISIX

- [CVE-2022-24112](https://insights.sbomify.com/CVE-2022-24112/): Apache APISIX Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-25757](https://insights.sbomify.com/CVE-2022-25757/): Apache APISIX: the body_schema check in request-validation plugin can be bypassed (critical 9.8)
- [CVE-2026-31908](https://insights.sbomify.com/CVE-2026-31908/): Apache APISIX: forward auth plugin allows header injection (critical 9.1)
- [CVE-2026-75005](https://insights.sbomify.com/CVE-2026-75005/): Apache APISIX: Unauthenticated CPU-exhaustion DoS (high 8.7)
- [CVE-2025-27446](https://insights.sbomify.com/CVE-2025-27446/): Privilege escalation in Apache APISIX Java Plugin Runner (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13945 and fix it if it is affected.

What it is: CVE-2020-13945 is a medium-severity vulnerability in Apache APISIX, published on 7 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-13945 exists.

Affected packages and fixed versions:
- apisix (Bitnami): affected from 1.2.0; fixed in 1.5.1

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-2020-13945/ (Markdown: https://insights.sbomify.com/CVE-2020-13945/index.md)
```

## Sources

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

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