dbcve.org
Ccn LiteApplication

CVE-2017-12465

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
Multiple integer overflows in CCN-lite before 2.00 allow context-dependent attackers to have unspecified impact via vectors involving the (1) vallen variable in the iottlv_parse_sequence function or (2) typ, vallen and i variables in the localrpc_parse function.

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

Integer overflow vulnerabilities in CCN-lite versions before 2.00 in the iottlv_parse_sequence and localrpc_parse functions allow attackers to manipulate the vallen, typ, and i variables to cause buffer overflows or memory corruption during TLV and RPC packet parsing.

MitigationUpgrade CCN-lite to version 2.00 or later which contains the fix. If upgrading is not possible, implement input validation and bounds checking on the vallen, typ, and i variables in the affected parsing functions before they are used 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. Confirm CCN-lite is present in your environment
    Search for CCN-lite files, libraries, or binaries using file system queries (e.g., find / -name '*ccnlite*' 2>/dev/null, check package managers, or look for ccnd/ccn-lite related processes)
    Affected if CCN-lite is installed or embedded in your system
  2. Identify the installed CCN-lite version
    Run version commands if available (e.g., ccnd -v, ccntlv -version), check library version symbols, or examine version headers in source code if you have access to the codebase
    Affected if The version is any release prior to 2.0.0 (e.g., 1.x.x, 0.x.x)
  3. Determine if TLV packet parsing is in use
    Monitor or inspect network traffic and application logs for TLV (Type-Length-Value) protocol usage, or check application configurations that invoke the iottlv_parse_sequence function
    Affected if Your application or service processes TLV packets using CCN-lite
  4. Determine if RPC functionality is in use
    Inspect application configurations, logs, or network activity for RPC-based communications, or check if the localrpc_parse function is being invoked
    Affected if Your application or service uses CCN-lite RPC features
  5. Verify the vulnerable parsing code exists
    If you have access to the CCN-lite source, search for the iottlv_parse_sequence and localrpc_parse functions and inspect the use of vallen, typ, and i variables for overflow-prone operations (e.g., unchecked arithmetic before memory allocation)
    Affected if The source code contains these functions without integer overflow safeguards

You are affected if CCN-lite version is below 2.0.0 AND your environment actively parses TLV packets or uses RPC functionality through CCN-lite.

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 CCN-lite to version 2.00 or later which contains the fix. If upgrading is not possible, implement input validation and bounds checking on the vallen, typ, and i variables in the affected parsing functions before they are used in memory operations.

Recommended fix Moderate confidence

2.0.0

  1. Upgrade CCN-lite to version 2.0.0 or later to resolve the integer overflow vulnerabilities in the iottlv_parse_sequence and localrpc_parse functions

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
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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