CVE-2018-16664
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 · uneditedAn issue was discovered in Contiki-NG through 4.1. There is a buffer overflow in lvm_set_type in os/storage/antelope/lvm.c while parsing AQL (lvm_set_op, lvm_set_relation, lvm_set_operand).
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 confidenceA buffer overflow vulnerability exists in the lvm_set_type function in os/storage/antelope/lvm.c of Contiki-NG through version 4.1. The overflow occurs during AQL (Antelope Query Language) parsing when handling the lvm_set_op, lvm_set_relation, and lvm_set_operand functions, allowing potential memory corruption during query processing.
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<= 4.1CVSS 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
- Local
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Contiki-NG deploymentDetermine if the target system runs Contiki-NG as its embedded operating system. This may require reviewing firmware documentation, build configurations, or system specifications.Affected if The system is confirmed to use Contiki-NG as the OS
-
Check Contiki-NG versionLocate the Contiki-NG version information in the firmware build files, release documentation, or version headers. Compare the installed version against the affected range of <= 4.1.Affected if The installed Contiki-NG version is 4.1 or earlier
-
Verify antelope storage module inclusionInspect the compiled firmware or build system to confirm the presence of os/storage/antelope/lvm.c in the image. This module implements the database functionality.Affected if The antelope/lvm.c module is compiled into the firmware
-
Confirm AQL query processing is activeDetermine whether the system performs AQL (Antelope Query Language) query operations using the lvm_set_op, lvm_set_relation, or lvm_set_operand functions. Review application code that invokes database queries.Affected if The system executes AQL queries against the antelope database storage layer
A system is affected if it runs Contiki-NG version 4.1 or earlier, includes the antelope storage module, and processes AQL queries which trigger the vulnerable lvm_set_type function in lvm.c.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Contiki-NG to a version beyond 4.1 that includes the patch, or implement proper bounds checking in the AQL parsing functions (lvm_set_op, lvm_set_relation, lvm_set_operand) before copying data into fixed-size buffers in lvm_set_type.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-16664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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