dbcve.org
Contiki Ng.Operating system · Contiki Ng

CVE-2018-16665

MEDIUM · 6.1 CVSS v3.0 Published 2018-09-07
Fix available
A fix is available. Upgrade to after 4.1 or later.
See remediation →
63/100
Remediation priority · Elevated
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
An issue was discovered in Contiki-NG through 4.1. There is a buffer overflow while parsing AQL in lvm_shift_for_operator in os/storage/antelope/lvm.c.

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 Contiki-NG through version 4.1 in the Antelope database storage layer (lvm.c). The vulnerability occurs in the lvm_shift_for_operator function while parsing AQL (Antelope Query Language), where insufficient bounds checking allows a buffer overflow.

MitigationUpdate Contiki-NG to a version beyond 4.1 that contains the fix, or apply a patch to lvm.c adding proper bounds validation in the lvm_shift_for_operator function before deployment.

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
Contiki Ng.Operating system
Affected:<= 4.1

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 Contiki-NG is present
    Identify if your codebase or firmware is built on Contiki-NG by checking for Contiki-NG project files, makefiles, or directory structure
    Affected if Contiki-NG is not present in your environment
  2. Determine Contiki-NG version
    Check the version tag or version file in your Contiki-NG installation: look for a version tag via git tag or check a version definition file
    Affected if Version is 4.1 or lower (any version up to and including 4.1)
  3. Locate lvm.c in the source tree
    Search for the file lvm.c in your Contiki-NG source, typically found in an apps or database-related directory
    Affected if The lvm.c file exists, indicating the Antelope database component is included in your build
  4. Check for the vulnerable function
    Search the lvm.c source file for the function name lvm_shift_for_operator to confirm the vulnerable code is present
    Affected if The lvm_shift_for_operator function exists in your lvm.c file

You are affected if your environment uses Contiki-NG version 4.1 or lower that includes the Antelope database storage layer (lvm.c) with the lvm_shift_for_operator function for parsing AQL queries.

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.

From vendor data
Upgrade available Upgrade to a release after 4.1
Interim mitigation

Update Contiki-NG to a version beyond 4.1 that contains the fix, or apply a patch to lvm.c adding proper bounds validation in the lvm_shift_for_operator function before deployment.

Fix this in Contiki Ng. Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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