# CVE-2021-43175: Auth bypass in GOautodial API

> Attackers can bypass authentication in the GOautodial API by providing arbitrary credentials, gaining unauthorized access to API functions.

- **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:** 7 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jgjr-5rhg-5c7w

## What is CVE-2021-43175?

CVE-2021-43175 is a high-severity authentication bypass vulnerability in GOautodial API, published on 7 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The GOautodial API prior to commit 3c3a979 made on October 13th, 2021 exposes an API router that accepts a username, password, and action that routes to other PHP files that implement the various API functions. Vulnerable versions of GOautodial validate the username and password incorrectly, allowing the caller to specify any values for these parameters and successfully authenticate. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C

Weakness: CWE-287 (Improper Authentication), CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2021-43175?

It affects 2 products.


Products: Goautodial Goautodial, Goautodial Goautodial Api.

## How do I fix CVE-2021-43175?

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

## Is CVE-2021-43175 being exploited?

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

## Other vulnerabilities in GOautodial API

- [CVE-2021-43176](https://insights.sbomify.com/CVE-2021-43176/): Path traversal in GOautodial API (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43175 and fix it if it is affected.

What it is: CVE-2021-43175 is a high-severity authentication bypass vulnerability in GOautodial API, published on 7 Dec 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-2021-43175 in the wild and no public exploit code.

Affected product: GOautodial API. 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-2021-43175/ (Markdown: https://insights.sbomify.com/CVE-2021-43175/index.md)
```

## Sources

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

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