dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2024-55570

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
/api/user/users in the web GUI for the Cubro EXA48200 network packet broker (build 20231025055018) fixed in V5.0R14.5P4-V3.3R1 allows remote authenticated users of the application to increase their privileges by sending a single HTTP PUT request with rolename=Administrator, aka incorrect access control.

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

This is an incorrect access control vulnerability in the /api/user/users endpoint of the Cubro EXA48200 network packet broker web GUI. Authenticated users can escalate their privileges to Administrator by sending a crafted HTTP PUT request containing rolename=Administrator, bypassing intended role-based access controls.

MitigationUpdate to the fixed firmware version V5.0R14.5P4-V3.3R1 or later. Review existing user accounts to ensure no unauthorized privilege escalation has occurred.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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 Cubro EXA48200 device in environment
    Inventory network devices and confirm the presence of Cubro EXA48200 packet brokers. Check network diagrams, device inventories, or SNMP/syslog sources for this specific model.
    Affected if A Cubro EXA48200 device is present in the environment and is accessible on the network.
  2. Check firmware version
    Access the device web GUI or CLI and navigate to the firmware/version information page. Compare the installed firmware version against the fixed version V5.0R14.5P4-V3.3R1.
    Affected if The installed firmware version is earlier than V5.0R14.5P4-V3.3R1.
  3. Verify web GUI accessibility
    Confirm the web interface is accessible via HTTP/HTTPS. Check if the /api/user/users endpoint responds to authenticated requests.
    Affected if The web GUI is exposed and accessible to authenticated users.
  4. Review user accounts for privilege escalation
    Log into the web GUI with a standard user account and navigate to the user management section. Check for any accounts that have the Administrator role that should not have elevated privileges.
    Affected if Standard authenticated users can access user management and modify their own role to Administrator.

You are affected if you have a Cubro EXA48200 device running firmware earlier than V5.0R14.5P4-V3.3R1 with its web GUI accessible to non-administrator users.

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

Update to the fixed firmware version V5.0R14.5P4-V3.3R1 or later. Review existing user accounts to ensure no unauthorized privilege escalation has occurred.

Recommended fix Moderate confidence

V5.0R14.5P4 or V3.3R1 (check Cubro support for exact version compatibility)

  1. 1. Identify the current firmware version of the Cubro EXA48200 device by accessing the web GUI or using the device's management interface
  2. 2. Download the fixed firmware version V5.0R14.5P4 (or V3.3R1, whichever is compatible with your device model) from the official Cubro support portal
  3. 3. Access the device's administration interface and navigate to the firmware upgrade section
  4. 4. Upload and apply the new firmware version, following the vendor's upgrade instructions
  5. 5. After the upgrade completes, verify that the /api/user/users endpoint now properly enforces role-based access controls
  6. 6. Confirm that regular users can no longer escalate privileges to Administrator through API requests
Caveat Review Cubro release notes for any configuration or feature changes between your current build and the fixed version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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