# CVE-2021-4230: Airfield Online MySQL Backup improper authentication

> An attacker can access sensitive MySQL backup data without authentication due to improper access controls in Airfield Online.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** 24 May 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-4gxw-qgvh-3768

## What is CVE-2021-4230?

CVE-2021-4230 is a low-severity authentication bypass vulnerability in unspecified Airfield Online, published on 24 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in Airfield Online and classified as problematic. This vulnerability affects the path /backups/ of the MySQL backup handler. An attacker is able to get access to sensitive data without proper authentication. It is recommended to the change the configuration settings.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Airfield Online Project Airfield Online.

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

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

## Is CVE-2021-4230 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-4230 is a low-severity authentication bypass vulnerability in unspecified Airfield Online, published on 24 May 2022. 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-4230 in the wild and no public exploit code.

Affected product: unspecified Airfield Online. 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-4230/ (Markdown: https://insights.sbomify.com/CVE-2021-4230/index.md)
```

## Sources

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

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