dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2024-24899

HIGH · 7.2 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 →
78/100
Remediation priority · High
Remotely reachable 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 an OS Command ('OS Command Injection') vulnerability in openEuler aops-zeus on Linux allows Command Injection. This vulnerability is associated with program files https://gitee.Com/openeuler/aops-zeus/blob/master/zeus/conf/constant.Py. This issue affects aops-zeus: from 1.2.0 through 1.4.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

OS command injection vulnerability in openEuler aops-zeus component allows attackers to execute arbitrary OS commands via improper neutralization of special elements in the constant.py file. The vulnerability exists in versions 1.2.0 through 1.4.0, where user-controlled input is likely passed unsanitized to shell execution functions.

MitigationUpgrade aops-zeus to a version beyond 1.4.0. If immediate patching is unavailable, restrict network access to the service and implement input validation as a compensating control until the 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
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Verify aops-zeus is installed
    Query the package manager for the aops-zeus package (e.g., rpm -qa | grep aops-zeus or dnf list installed aops-zeus)
    Affected if The package is not found on the system, then the vulnerability does not apply
  2. Determine the installed version
    Run a version query on the aops-zeus package (e.g., rpm -q aops-zeus --queryformat '%{VERSION}-%{RELEASE}' or check the installed package metadata)
    Affected if The installed version falls within the range 1.2.0 through 1.4.0 (including 1.2.0 and 1.4.0)
  3. Locate the constant.py file
    Search for the constant.py file in the aops-zeus installation directory - typical locations include /usr/lib/python*/site-packages/aops_zeus/ or the application's base directory
    Affected if The file exists and contains code that passes variables to shell execution functions (look for patterns like os.system, subprocess.call, or similar with unsanitized input)
  4. Check if the service is network-accessible
    Review the service configuration and running processes to determine if aops-zeus exposes a network listener or API (check listening ports, firewall rules, or service startup parameters)
    Affected if The service is exposed to network access, increasing the likelihood of exploitation

A system is affected if aops-zeus is installed with version 1.2.0 through 1.4.0 and the vulnerable constant.py file with unsafe shell execution is present and accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade aops-zeus to a version beyond 1.4.0. If immediate patching is unavailable, restrict network access to the service and implement input validation as a compensating control until the fix is applied.

Recommended fix Moderate confidence

aops-zeus version 1.5.0 or later

  1. Identify the current installed version of aops-zeus using the package manager or by checking the version file
  2. Backup the current installation and any configuration files
  3. Upgrade aops-zeus to version 1.5.0 or later using the package manager (e.g., `dnf update aops-zeus` or `yum update aops-zeus`)
  4. Verify the upgraded version matches the fixed release
  5. Restart any services dependent on aops-zeus
  6. Test that the application functions correctly with the updated version
Caveat Review release notes for any breaking changes between 1.4.0 and the target version

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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