# CVE-2020-20183: Missing authorization in n/a

> Attackers can access admin pages and gain privileges via insecure direct object references in Zyxel P1302-T10 firmware.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 14 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r5ph-fc45-cwp3

## What is CVE-2020-20183?

CVE-2020-20183 is a high-severity missing authorization vulnerability in n/a, published on 14 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Insecure direct object reference vulnerability in Zyxel’s P1302-T10 v3 with firmware version 2.00(ABBX.3) and earlier allows attackers to gain privileges and access certain admin pages.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

It affects 1 product.


Products: Zyxel P1302-T10 V3 Firmware.

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

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

## Is CVE-2020-20183 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-20183 is a high-severity missing authorization vulnerability in n/a, published on 14 Dec 2020. 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-2020-20183 in the wild and no public exploit code.

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

## Sources

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

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