dbcve.org
Ccn LiteApplication

CVE-2017-12472

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
ccnl-ext-mgmt.c in CCN-lite before 2.00 allows context-dependent attackers to have unspecified impact by leveraging missing NULL pointer checks after ccnl_malloc.

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

The CCN-lite networking software (versions before 2.00) contains missing NULL pointer checks in ccnl-ext-mgmt.c following ccnl_malloc memory allocation calls. When ccnl_malloc fails and returns NULL, the code proceeds to use the NULL pointer without validation, leading to NULL pointer dereferences that can cause denial of service or potentially enable code execution.

MitigationUpgrade to CCN-lite version 2.00 or later which includes proper NULL pointer validation after memory allocations in the affected code path.

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. Identify CCN-lite installation and version
    Check for CCN-lite installation by looking for the source directory, package installation, or executable binary. Look for version information in source files (version.h, configure.ac, or a VERSION file), or run 'grep -r "VERSION"' or './configure --version' if available. If CCN-lite is installed as a package, use the system package manager to query the version.
    Affected if The installed version is any release before 2.0.0 (e.g., 1.x.x series, or versions without the patch that adds NULL checks).
  2. Locate the affected source file
    Search for the file ccnl-ext-mgmt.c in the CCN-lite source tree or installation directory. This file contains the vulnerable code path with missing NULL pointer validation after ccnl_malloc calls.
    Affected if The file ccnl-ext-mgmt.c exists in the installation and is being compiled into the binary or library.
  3. Verify the code path is reachable
    Inspect ccnl-ext-mgmt.c to determine if the code using ccnl_malloc without NULL checks is actually compiled. Look for the specific functions that call ccnl_malloc and are invoked during normal operation. Check build configuration to confirm the management extensions module is enabled.
    Affected if The management extension code (the affected code path) is compiled and the program processes network management messages or performs related operations that trigger the vulnerable ccnl_malloc calls.

You are affected if CCN-lite version is below 2.0.0 AND the ccnl-ext-mgmt.c file is present and compiled into a deployed binary that processes network traffic.

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

Upgrade to CCN-lite version 2.00 or later which includes proper NULL pointer validation after memory allocations in the affected code path.

Recommended fix High confidence

CCN-lite 2.0.0 or later

  1. 1. Identify the current CCN-lite version in use by checking the source code version file or build configuration
  2. 2. Download CCN-lite version 2.0.0 or later from the official repository at github.com/CCN-lite/ccn-lite
  3. 3. Review the release notes and changelog for version 2.0.0 to understand changes
  4. 4. Create a backup of the current CCN-lite installation and configuration
  5. 5. Replace the vulnerable ccnl-ext-mgmt.c file with the version from 2.0.0 or later, OR install the complete version 2.0.0 release
  6. 6. Rebuild the CCN-lite components to incorporate the fixes
  7. 7. Test the rebuilt system to ensure functionality is maintained
  8. 8. Deploy the updated version to production environments

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

Fix this in Ccn Lite Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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