dbcve.org
AtuneApplication · Huawei

CVE-2021-33658

HIGH · 7.8 CVSS v3.1 Published 2022-03-11
Fix available
A fix is available. Upgrade to after 0.8 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

atune before version 0.3-0.8 ships with authentication disabled by default on its web interface. A local user can use curl to access this unauthenticated local URL and escalate privileges to root or modify arbitrary files on the system.

MitigationEnable authentication in atune's configuration file or upgrade to version 0.3-0.8 or later where authentication is enforced by default.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AtuneApplication
Affected:>= 0.3, <= 0.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Atune version
    Run 'rpm -qa | grep atune' or 'dpkg -l | grep atune' to list the installed Atune package and its version number
    Affected if Version is 0.3, 0.4, 0.5, 0.6, 0.7, or 0.8
  2. Confirm Atune web service is running
    Run 'netstat -tlnp' or 'ss -tlnp' and look for ports 8080 or 8443 listening, or check process list for atune-related Java or Python processes serving the web interface
    Affected if The Atune web interface daemon is active and listening on a network port
  3. Test web interface authentication
    Use curl to send an HTTP request to the local Atune API endpoint without any credentials: 'curl -I http://localhost:8080/api/' or the port observed in step 2
    Affected if The request returns HTTP 200 or succeeds without requiring authentication (no 401 or 403 response)
  4. Inspect authentication configuration
    Locate atune configuration files (commonly in /etc/atune/ or /opt/atune/conf/) and check for 'authentication.enabled', 'auth.enabled', or similar settings
    Affected if Authentication is explicitly set to false, or the setting is absent (defaulting to disabled in affected versions)

The environment is affected if Atune version 0.3-0.8 is installed, the web interface is running, and unauthenticated access to local API endpoints is possible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 0.8
Interim mitigation

Enable authentication in atune's configuration file or upgrade to version 0.3-0.8 or later where authentication is enforced by default.

Recommended fix Moderate confidence

Upgrade to atune version > 0.8 (or the latest stable release where authentication is enabled by default)

  1. 1. Identify the current installed version of atune using: atune --version or checking the package manager
  2. 2. If running version 0.3 through 0.8, plan for an upgrade to a version beyond 0.8 where authentication is enforced by default
  3. 3. Before upgrading, review the atune documentation for any configuration changes required
  4. 4. Perform the upgrade using the package manager or source installation method appropriate for your distribution
  5. 5. After upgrade, verify authentication is enabled by default by checking the configuration file (typically atune.conf)
  6. 6. Test that the atune service requires authentication before allowing access to the API interface
Caveat Review release notes for any configuration or API changes between 0.8 and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Atune Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33658 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33658 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data