dbcve.org
Rdkb CcsppandmApplication · Rdkcentral

CVE-2019-6964

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 over-read in Service_SetParamStringValue in cosa_x_cisco_com_ddns_dml.c of the RDK RDKB-20181217-1 CcspPandM module may allow attackers with login credentials to achieve information disclosure and code execution by crafting an AJAX call responsible for DDNS configuration with an exactly 64-byte username, password, or domain, for which the buffer size is insufficient for the final '\0' character. This is related to the CcspCommonLibrary and WebUI modules.

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 heap-based buffer over-read vulnerability exists in the Service_SetParamStringValue function in cosa_x_cisco_com_ddns_dml.c of the RDK RDKB CcspPandM module. When processing DDNS configuration parameters (username, password, or domain), the function allocates a fixed 64-byte buffer but fails to account for the null terminator, allowing authenticated attackers to read beyond heap buffer boundaries via crafted 64-byte AJAX calls, potentially leading to information disclosure and arbitrary code execution.

MitigationApply the vendor patch for RDKB-20181217-1 or later versions. Ensure all string buffers are sized to accommodate the string data plus the null terminator, and implement proper bounds checking in the Service_SetParamStringValue function.

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. Locate the CcspPandM module version
    Check the installed RDKB firmware version or examine the CcspPandM component version on the device (typically found in /version or via sysinfo). Compare against the affected version rdkb-20181217-1.
    Affected if The installed CcspPandM version equals rdkb-20181217-1 or is based on this release.
  2. Verify DDNS feature is enabled
    Access the device's web interface or CLI and check the DDNS (Dynamic DNS) configuration settings. Look for whether DDNS service is configured with a username, password, or domain parameter.
    Affected if DDNS is enabled and configured with user-supplied credentials or domain values that would be processed by Service_SetParamStringValue.
  3. Confirm the vulnerable code component exists
    Check for the presence of cosa_x_cisco_com_ddns_dml.c or its compiled binary in the CcspPandM module directory on the device filesystem.
    Affected if The file cosa_x_cisco_com_ddns_dml.c exists in the build, indicating the vulnerable DDNS processing code is present.
  4. Check web management interface accessibility
    Verify if the device's AJAX/web management interface is accessible remotely or via LAN. The vulnerability is triggered through crafted AJAX calls to DDNS configuration parameters.
    Affected if The web management interface (which handles the AJAX calls for DDNS configuration) is accessible to authenticated users.

You are affected if your RDKB firmware uses CcspPandM version rdkb-20181217-1 and has DDNS feature enabled, as the heap over-read only occurs when processing DDNS configuration parameters through the AJAX interface.

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 the vendor patch for RDKB-20181217-1 or later versions. Ensure all string buffers are sized to accommodate the string data plus the null terminator, and implement proper bounds checking in the Service_SetParamStringValue function.

Fix this in Rdkb Ccsppandm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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