dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2024-5168

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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 access control vulnerability in Prodys' Quantum Audio codec affecting versions 2.3.4t and below. This vulnerability could allow an unauthenticated user to bypass authentication entirely and execute arbitrary API requests against the web application.

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

Improper access control in Prodys Quantum Audio codec versions 2.3.4t and below allows unauthenticated attackers to completely bypass authentication on the web interface. This critical flaw enables remote, unauthenticated execution of arbitrary API requests with administrative-level privileges, effectively giving attackers full control over the codec device.

MitigationUpgrade the Prodys Quantum Audio codec to a version higher than 2.3.4t that includes the access control fix. If immediate patching is not feasible, restrict network access to the web interface using firewall rules or VPN tunneling to prevent unauthorized external access.

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

CVSS:3.1/AV:N/AC:L/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. Identify the installed version of Prodys Quantum Audio codec
    Access the web interface admin panel or system information page to view the current software version. If you have CLI access, check the firmware version through the device's command-line interface.
    Affected if The displayed version is 2.3.4t or any version lower than 2.3.4t.
  2. Confirm the web interface is enabled
    Check the device configuration or settings to verify whether the web-based management interface is turned on.
    Affected if The web interface is currently enabled and operational.
  3. Assess network accessibility of the web interface
    Determine if the web interface is reachable from network locations outside your trusted internal network, such as from the internet or untrusted subnets.
    Affected if The web interface is exposed to untrusted networks or the public internet without VPN or firewall protection.
  4. Verify authentication enforcement on the web interface
    Attempt to access API endpoints or administrative functions without providing credentials. If unauthenticated access succeeds, the authentication bypass is present.
    Affected if Unauthenticated requests to API endpoints or admin functions return successful responses instead of requiring login.

You are affected if the installed version is 2.3.4t or below and the web interface is enabled and accessible on your network, because this combination allows unauthenticated attackers to execute administrative API requests.

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 the Prodys Quantum Audio codec to a version higher than 2.3.4t that includes the access control fix. If immediate patching is not feasible, restrict network access to the web interface using firewall rules or VPN tunneling to prevent unauthorized external access.

Recommended fix Moderate confidence

Version higher than 2.3.4t (contact Prodys for exact fixed release)

  1. Contact Prodys technical support to obtain the latest patched version of the Quantum Audio codec
  2. Request specific information about the fixed release version that addresses CVE-2024-5168
  3. Plan upgrade in a staging environment to validate functionality
  4. Schedule maintenance window for production upgrade
  5. Upgrade Quantum Audio codec to the version provided by Prodys that includes the authentication bypass fix
  6. Verify the web interface is accessible and authentication is properly enforced after upgrade
  7. Test that unauthenticated API requests are no longer possible
  8. Update inventory/documentation to reflect the new version
Caveat Contact Prodys for release notes; minor version upgrades typically preserve configuration but validate in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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