dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-24897

HIGH · 8.1 CVSS v3.1 Published 2024-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in openEuler A-Tune-Collector on Linux allows Command Injection. This vulnerability is associated with program files https://gitee.Com/openeuler/A-Tune-Collector/blob/master/atune_collector/plugin/monitor/process/sched.Py. This issue affects A-Tune-Collector: from 1.1.0-3 through 1.3.0.

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 · moderate confidence

A command injection vulnerability exists in openEuler A-Tune-Collector's process monitoring component (sched.py). The vulnerability stems from improper neutralization of special elements in user-controlled input that gets passed to system commands, allowing an attacker to execute arbitrary commands on the affected system.

MitigationUpgrade A-Tune-Collector to a version beyond 1.3.0. If no patch is available, implement input validation and sanitization on all parameters passed to system calls within the sched.py file, or disable the affected process monitoring plugin until a fix is applied.

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

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/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. Confirm A-Tune-Collector is installed
    Check if the A-Tune-Collector package or service exists on the system. Look for the atune-collector package via package manager (rpm -qa | grep atune) or check for the service process.
    Affected if The package or service named A-Tune-Collector or atune-collector is found on the system.
  2. Identify installed A-Tune-Collector version
    Query the package version using the system package manager. For RPM-based systems: rpm -qa | grep atune-collector or rpm -qi atune-collector. Compare the version number to 1.3.0.
    Affected if The installed version is 1.3.0 or lower (the fixed version is beyond 1.3.0).
  3. Locate the sched.py component
    Find the sched.py file within the A-Tune-Collector installation directory. Common paths include /usr/lib/atune-collector/ or the installation root. Search for: find / -name sched.py 2>/dev/null.
    Affected if The sched.py file exists in the A-Tune-Collector installation directory.
  4. Verify process monitoring plugin is active
    Check the A-Tune-Collector configuration or running processes to determine if the process monitoring functionality (sched.py) is enabled or actively running. Inspect configuration files in the collector directory for process monitoring settings.
    Affected if The process monitoring plugin is enabled or running, exposing the vulnerable code path.
  5. Inspect for user-controlled input to system calls
    Examine the sched.py file for system command execution (os.system, subprocess calls, shell=True) that accepts external input. Look for parameters that could be influenced by user input without sanitization.
    Affected if The code contains unsanitized input passed to system command execution functions.

A system is affected if A-Tune-Collector version 1.3.0 or lower is installed, the sched.py process monitoring component exists, and the vulnerable command injection path is accessible and active.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade A-Tune-Collector to a version beyond 1.3.0. If no patch is available, implement input validation and sanitization on all parameters passed to system calls within the sched.py file, or disable the affected process monitoring plugin until a fix is applied.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24897 — 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-2024-24897 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