dbcve.org
Vap2500 FirmwareOperating system · Arris

CVE-2024-5194

HIGH · 7.2 CVSS v3.1 Published 2024-05-22
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
A vulnerability was found in Arris VAP2500 08.50. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the file /assoc_table.php. The manipulation of the argument id leads to command injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-265831.

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

A command injection vulnerability exists in the Arris VAP2500 firmware version 08.50. The vulnerability is located in the /assoc_table.php file where the 'id' parameter is not properly sanitized, allowing remote authenticated attackers to execute arbitrary OS commands via crafted input.

MitigationApply vendor firmware patch if available; otherwise implement network segmentation to limit exposure, disable remote management interfaces if not required, or replace the end-of-life device. Implement input validation and sanitization on the affected parameter as a compensating control.

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
Vap2500 FirmwareOperating system
Affected:= 08.50

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. Confirm device model is Arris VAP2500
    Access the device web interface or check the administrative console to identify the exact model number. This vulnerability applies only to the VAP2500 hardware model.
    Affected if The device is not an Arris VAP2500 unit
  2. Verify firmware version is 08.50
    Navigate to the device administrative interface (typically via web browser at the device IP) and locate the firmware version information in System or Status settings. Compare against the affected version.
    Affected if Firmware version is not exactly 08.50
  3. Check if web management interface is accessible
    Attempt to access the /assoc_table.php endpoint via HTTP or HTTPS (e.g., http://[device-ip]/assoc_table.php). Verify the page loads or responds.
    Affected if The web interface and /assoc_table.php are not accessible from the network
  4. Confirm remote authentication is enabled
    In the device administrative interface, examine the remote management or administration settings. Determine if remote HTTP/HTTPS access is permitted and check whether default credentials remain in use.
    Affected if Remote authentication is disabled or the management interface is not accessible to network attackers
  5. Verify the id parameter accepts unsanitized input
    If authenticated access is available, examine how the id parameter in /assoc_table.php is handled. This requires code review or testing to confirm the parameter passes input to system calls without sanitization.
    Affected if The id parameter properly sanitizes input or the endpoint does not process the id parameter

The device is affected only if it is an Arris VAP2500 running firmware version 08.50 with remote web management enabled and the /assoc_table.php endpoint accessible to an authenticated attacker.

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

Apply vendor firmware patch if available; otherwise implement network segmentation to limit exposure, disable remote management interfaces if not required, or replace the end-of-life device. Implement input validation and sanitization on the affected parameter as a compensating control.

Fix this in Vap2500 Firmware 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 help mitigating

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-5194 — 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-5194 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