dbcve.org
Ccn LiteApplication

CVE-2018-7039

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-14
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
CCN-lite 2.0.0 Beta allows remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact because the ccnl_ndntlv_prependBlob function in ccnl-pkt-ndntlv.c can be called with wrong arguments. Specifically, there is an incorrect integer data type causing a negative third argument in some cases of crafted TLV data with inconsistent length information.

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

Buffer overflow vulnerability in CCN-lite 2.0.0 Beta's ccnl_ndntntlv_prependBlob function in ccnl-pkt-ndntlv.c where an incorrect integer data type causes a negative third argument when processing crafted TLV data with inconsistent length information, allowing remote attackers to overflow buffers or cause denial of service.

MitigationFix the integer data type mismatch to ensure length values cannot be negative, and add proper validation of TLV length fields against actual data size before use in memory operations.

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
Ccn LiteApplication
Affected:= 2.0.0

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.0/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. Verify CCN-lite installation and version
    Run `ccnl-lite -v` or check package manager for ccn-lite version. Also check any source directories for version.h or configure.ac files that state the version.
    Affected if Version is 2.0.0 Beta (2.0.0)
  2. Locate the vulnerable source file
    Search for ccnl-pkt-ndntlv.c in the CCN-lite installation directory or source tree using `find . -name ccnl-pkt-ndntlv.c`.
    Affected if The file exists in the CCN-lite codebase in use.
  3. Confirm the vulnerable function exists
    Search for 'ccnl_ndntntlv_prependBlob' in the codebase using `grep -r ccnl_ndntntlv_prependBlob .` or examine the ccnl-pkt-ndntlv.c file directly.
    Affected if The function ccnl_ndntntlv_prependBlob is present in the code.
  4. Determine if NDN-TLV packet parsing is enabled
    Check build configuration files (Makefile, config.h) or CCN-lite configuration for NDN-TLV protocol support. Look for compile flags like `-DCCNL_DEFAULT_ENDPOINT_NDNTLV` or similar NDN-TLV related defines.
    Affected if NDN-TLV protocol support is compiled into the binary or enabled in configuration.
  5. Inspect runtime packet processing
    If CCN-lite is running, monitor for NDN-TLV formatted traffic. Review logs or capture network traffic on the CCN端口 to identify if NDN-TLV packets are being processed.
    Affected if The system processes NDN-TLV formatted network packets.

A system is affected if CCN-lite version 2.0.0 Beta is installed, the vulnerable ccnl_ndntntlv_prependBlob function exists, and NDN-TLV packet parsing is enabled or in use.

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

Fix the integer data type mismatch to ensure length values cannot be negative, and add proper validation of TLV length fields against actual data size before use in memory operations.

Recommended fix Moderate confidence

A stable release of CCN-lite subsequent to version 2.0.0 (e.g., the latest stable release available in the repository)

  1. 1. Identify the current CCN-lite version in use by checking the software build or package metadata
  2. 2. Obtain a stable release of CCN-lite newer than version 2.0.0 from the official repository at github.com/c-cn-l/CCN-lite
  3. 3. Replace the vulnerable CCN-lite installation with the newer stable version
  4. 4. Rebuild or reinstall the software with the new version
  5. 5. Verify the installation by checking that the version number no longer shows 2.0.0
  6. 6. Test that CCN-lite functionality operates normally with the new version
Caveat Review release notes of the target version for any API changes or backward compatibility considerations before upgrading

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

Fix this in Ccn Lite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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