# CVE-2021-33658: Missing authorization in atune

> Local attackers can escalate privileges or modify files via the atune interface because authentication is disabled by default in openEuler.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-w6wx-x6vc-9hfh, OESA-2022-1541

## What is CVE-2021-33658?

CVE-2021-33658 is a high-severity missing authorization vulnerability in openEuler atune, published on 11 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

atune before 0.3-0.8 log in as a local user and run the curl command to access the local atune url interface to escalate the local privilege or modify any file. Authentication is not forcibly enabled in the default configuration.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Huawei Atune.

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

Upgrade to a fixed version.

## Is CVE-2021-33658 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-33658 is a high-severity missing authorization vulnerability in openEuler atune, published on 11 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-33658 in the wild and no public exploit code.

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

## Sources

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

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