dbcve.org
MangoApplication · Radixiot

CVE-2024-37845

HIGH · 7.2 CVSS v3.1 Published 2024-10-25
Fix available
A fix is available. Upgrade to 5.2.0 or later.
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
MangoOS before 5.2.0 was discovered to contain an authenticated remote code execution (RCE) vulnerability via the Active Process Command feature.

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

MangoOS before version 5.2.0 contains an authenticated remote code execution vulnerability in the Active Process Command feature. This allows an authenticated attacker to execute arbitrary commands on the underlying operating system. With a CVSS score of 7.2, the vulnerability is exploitable over the network but requires valid credentials.

MitigationUpgrade MangoOS to version 5.2.0 or later to remediate this vulnerability. If immediate upgrade is not possible, restrict access to the Active Process Command feature to a limited set of trusted users and monitor for suspicious command execution.

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
MangoApplication
Affected:< 5.2.0

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. Identify MangoOS version
    Access the MangoOS administrative interface and navigate to System > About or use the command line interface (if available) to retrieve the installed version number. Look for a version field displaying something like 'MangoOS vX.X.X' or check the system information panel.
    Affected if The installed version is below 5.2.0 (for example, 5.1.5, 5.0.0, or earlier)
  2. Locate Active Process Command feature
    In the MangoOS admin panel, search for a feature named 'Active Process Command', 'Process Control', or 'Command Execution' under the System, Administration, or Diagnostics menu sections. Alternatively, examine the configuration file (typically mango.conf or similar) for entries containing 'active_process_command', 'process_cmd', or 'exec_module'.
    Affected if The Active Process Command feature exists and is present in the configuration or menu
  3. Verify Active Process Command feature status
    Check whether the Active Process Command feature is enabled or disabled. In the admin interface, look for a toggle, checkbox, or status indicator next to the feature. In configuration files, look for a parameter like 'active_process_command_enabled=true' or 'process_cmd_enabled=1'.
    Affected if The feature is explicitly enabled or its status cannot be determined (assume enabled)
  4. Review access controls on the feature
    Examine user roles, permissions, or access control lists (ACLs) that govern who can access the Active Process Command feature. Look for user assignments, group permissions, or IP restrictions related to this functionality in the MangoOS administration panel.
    Affected if The feature is accessible to more than a limited set of trusted administrators, or if any authenticated user role has access to it

You are affected if your installed MangoOS version is below 5.2.0 AND the Active Process Command feature is enabled and accessible to your user account or role.

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 5.2.0 or later
Fixed in 5.2.0
Interim mitigation

Upgrade MangoOS to version 5.2.0 or later to remediate this vulnerability. If immediate upgrade is not possible, restrict access to the Active Process Command feature to a limited set of trusted users and monitor for suspicious command execution.

Recommended fix High confidence

5.2.0

  1. Back up the current Mango configuration and all existing data
  2. Download Mango version 5.2.0 from the official Mango sources
  3. Review the official upgrade documentation for your specific deployment method (standalone, Docker, etc.)
  4. Stop the Mango service before performing the upgrade
  5. Install or apply version 5.2.0 following the documented upgrade procedure
  6. Restart the Mango service after the upgrade is complete
  7. Verify the upgrade was successful by checking the version in the Mango UI or via CLI
  8. Test that the Active Process Command feature functions correctly in the upgraded version
Caveat Review release notes for 5.2.0 to check for any configuration or feature changes that may affect your existing setup

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

Fix this in Mango Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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