dbcve.org
Ccn LiteApplication

CVE-2017-12469

CRITICAL · 9.8 CVSS v3.0 Published 2018-02-07
Fix available
A fix is available. Upgrade to 2.0.0 or later.
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
Buffer overflow in util/ccnl-common.c in CCN-lite before 2.00 allows context-dependent attackers to have unspecified impact by leveraging incorrect memory allocation.

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 · moderate confidence

A buffer overflow vulnerability exists in util/ccnl-common.c of CCN-lite versions prior to 2.00, caused by incorrect memory allocation. The vulnerability has a critical CVSS score of 9.8, indicating potential for severe impact including remote code execution, though the exact exploitation details are context-dependent.

MitigationUpdate CCN-lite to version 2.00 or later to remediate the buffer overflow vulnerability caused by incorrect memory allocation. Given the critical severity, prioritize this update in deployment cycles.

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
    Check if CCN-lite is present on the system by searching for executables (ccn-lite-*) or libraries related to CCN-lite using commands like 'which ccn-lite-*' or 'find /usr -name "*ccn*" 2>/dev/null'
    Affected if CCN-lite is not found on the system - the CVE does not apply
  2. Identify CCN-lite version
    Run 'ccn-lite-ctrl -v' or 'ccn-lite-relay -v' to display the installed version. If these commands are not available, check package management tools (dpkg, rpm, pip) or examine source directories for version information
    Affected if The displayed version is below 2.0.0 (e.g., 1.x.x or earlier)
  3. Locate vulnerable source file
    If CCN-lite was built from source, search for the file util/ccnl-common.c in the installation or source tree using 'find . -name ccnl-common.c'
    Affected if The file exists and the associated CCN-lite binary/library is version 2.0.0 or later, but the source was not patched - compare version in step 2 first
  4. Confirm runtime usage of vulnerable component
    Review application logs, process lists, or configuration files to determine if CCN-lite utilities (ccn-lite-ctrl, ccn-lite-relay, ccn-lite-srv) are actively running or configured as services
    Affected if CCN-lite version is below 2.0.0 AND the utility binaries or libraries from util/ccnl-common.c are in active use

A user is affected if CCN-lite version 1.x.x or any version below 2.0.0 is installed and the ccn-lite utilities or libraries are in use on the system.

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
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Update CCN-lite to version 2.00 or later to remediate the buffer overflow vulnerability caused by incorrect memory allocation. Given the critical severity, prioritize this update in deployment cycles.

Recommended fix High confidence

CCN-lite 2.0.0

  1. 1. Check the currently installed CCN-lite version by running 'ccn-lite-version' or checking the package manager
  2. 2. Download CCN-lite version 2.0.0 or later from the official GitHub repository: https://github.com/ccn-lite/ccn-lite
  3. 3. If using a package manager, update to the latest version (e.g., 'apt-get update && apt-get install ccn-lite' or equivalent)
  4. 4. If building from source, clone the repository and checkout tag 'v2.0.0' or later: 'git clone https://github.com/ccn-lite/ccn-lite.git && cd ccn-lite && git checkout v2.0.0'
  5. 5. Rebuild and reinstall CCN-lite following the build instructions in the README
  6. 6. Verify the installed version is 2.0.0 or later
Caveat Review CCN-lite 2.0.0 release notes for API and configuration changes that may affect existing setups

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

Fix this in Ccn Lite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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