CVE-2018-16376
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 OpenJPEG 2.3.0. A heap-based buffer overflow was discovered in the function t2_encode_packet in lib/openmj2/t2.c. The vulnerability causes an out-of-bounds write, which may lead to remote denial of service or possibly unspecified other impact.
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 confidenceA heap-based buffer overflow vulnerability exists in OpenJPEG 2.3.0 within the t2_encode_packet function in lib/openmj2/t2.c. The vulnerability allows an out-of-bounds write due to improper bounds checking when processing JPEG2000 image data, potentially leading to denial of service or arbitrary code execution.
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= 2.3.0CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 OpenJPEG installation and versionRun 'openjpeg --version' or check the library file version using 'pkg-config --modversion openjpeg' or inspect the shared library file with 'strings' and grep for version infoAffected if The installed version is exactly 2.3.0
-
Locate the vulnerable t2.c source fileSearch for the file lib/openmj2/t2.c in the OpenJPEG installation directory or source treeAffected if The file exists at lib/openmj2/t2.c in the OpenJPEG installation
-
Verify the t2_encode_packet function is presentRun 'nm' or 'objdump' on the compiled library (libopenmj2.so or similar) and grep for 't2_encode_packet'Affected if The function symbol t2_encode_packet is exported in the compiled library
-
Check if applications use OpenJPEG for JPEG2000 processingIdentify processes or applications that link against OpenJPEG libraries (run 'ldd' on suspected applications or check for j2k/codestream processing)Affected if Applications process untrusted JPEG2000 image data using the affected OpenJPEG 2.3.0 library
-
Review application logs or crash reportsSearch system and application logs for heap corruption errors, segmentation faults, or buffer overflow indicators when processing JPEG2000 filesAffected if Crashes or heap corruption occur during JPEG2000 image decoding/encoding operations
You are affected if OpenJPEG version 2.3.0 is installed AND your applications process JPEG2000 image data using the vulnerable t2_encode_packet function in lib/openmj2/t2.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 to a patched version of OpenJPEG beyond 2.3.0 that addresses this vulnerability, or apply vendor-supplied patches to the t2_encode_packet function to enforce proper buffer boundary validation.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16376 — 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-16376 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