dbcve.org
Rdkb CcsppandmApplication · Rdkcentral

CVE-2019-6963

HIGH · 8.8 CVSS v3.0 Published 2019-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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 heap-based buffer overflow in cosa_dhcpv4_dml.c in the RDK RDKB-20181217-1 CcspPandM module may allow attackers with login credentials to achieve remote code execution by crafting a long buffer in the "Comment" field of an IP reservation form in the admin panel. This is related to the CcspCommonLibrary module.

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

Heap-based buffer overflow in the CcspPandM module's DHCPv4 configuration handler (cosa_dhcpv4_dml.c). The 'Comment' field in the IP reservation admin panel form lacks proper length validation before copying user input to a heap-allocated buffer, allowing authenticated attackers to overflow the heap and achieve remote code execution.

MitigationApply vendor patch for RDKB-20181217-1 or later; implement bounds checking on the Comment field input in cosa_dhcpv4_dml.c before heap buffer copy operations; consider input length limits at the web UI layer as defense-in-depth.

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
Rdkb CcsppandmApplication
Affected:= rdkb-20181217-1

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 RDKB Ccsppandm component version
    Check the installed version of the Ccsppandm package/module on the device. On RDKB-based devices, this may be viewable via the package management system, firmware metadata, or by querying the component directly if a version API exists.
    Affected if The installed version is rdkb-20181217-1 (exact match)
  2. Locate the vulnerable DHCPv4 configuration handler
    Search for the file cosa_dhcpv4_dml.c in the device firmware or source code repository. This file contains the DHCPv4 DML (Data Model Layer) functions for the CcspPandM module.
    Affected if The file exists and the build date/version corresponds to rdkb-20181217-1
  3. Verify the Comment field handling code is present
    Inspect the cosa_dhcpv4_dml.c file for the IP reservation configuration functions. Look for the code path that handles the Comment field input from the admin panel form.
    Affected if The Comment field processing code exists without proper length validation before heap buffer copy operations
  4. Confirm the IP reservation admin panel feature is accessible
    Check if the DHCPv4 IP reservation feature is enabled and accessible via the web admin panel or TR-069/ACS interface. This feature provides the input form where the Comment field vulnerability can be exploited.
    Affected if The IP reservation admin panel is accessible and accepts user input in the Comment field
  5. Determine if authentication is available for the admin panel
    Verify that the web management interface or TR-069 endpoint accepts authentication credentials. The vulnerability requires an authenticated attacker.
    Affected if Administrative authentication is enabled and functional on the device

The system is affected if it runs Rdkcentral Rdkb Ccsppandm version rdkb-20181217-1 and has the DHCPv4 IP reservation admin panel accessible with authentication enabled.

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 patch for RDKB-20181217-1 or later; implement bounds checking on the Comment field input in cosa_dhcpv4_dml.c before heap buffer copy operations; consider input length limits at the web UI layer as defense-in-depth.

Fix this in Rdkb Ccsppandm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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