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

> An unauthenticated remote attacker can access sensitive information in the Domoticz ISS Gateway REST API due to improper access control enforcement.

- **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:** 29 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x5c3-r34h-xf45

## What is CVE-2020-21990?

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

### Official description

Emmanuel MyDomoAtHome (MDAH) REST API REST API Domoticz ISS Gateway 0.2.40 is affected by an information disclosure vulnerability due to improper access control enforcement. An unauthenticated remote attacker can exploit this, via a specially crafted request to gain access to sensitive information.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Domoticz Mydomoathome.

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

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

## Is CVE-2020-21990 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-21990 is a high-severity missing authorization vulnerability in n/a, published on 29 Apr 2021. 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-21990 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-21990/ (Markdown: https://insights.sbomify.com/CVE-2020-21990/index.md)
```

## Sources

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

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