CVE-2018-18699
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 GoPro gpmf-parser 1.2.1. There is an out-of-bounds write in OpenMP4Source in GPMF_mp4reader.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 confidenceA high-severity out-of-bounds write vulnerability exists in GoPro gpmf-parser 1.2.1 within the OpenMP4Source function in GPMF_mp4reader.c. This memory corruption issue could allow an attacker to overwrite adjacent memory regions via specially crafted MP4 files, potentially leading to code execution or denial of service.
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= 1.2.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
- 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 gpmf-parser installationSearch for gpmf-parser library files or check application dependencies for 'gpmf-parser' package. On Linux, run: find / -name '*gpmf*' 2>/dev/null or check package managers. On Windows, search for GPMF_mp4reader.c or gpmf-parser.dll files.Affected if gpmf-parser library version 1.2.1 is found on the system
-
Verify the exact versionCheck the version string in the library binary, source code header, or build configuration. Look for version 1.2.1 in any gpmf-parser related file or metadata.Affected if The installed version is exactly 1.2.1
-
Confirm MP4 processing capabilityDetermine if any application or service on the system uses gpmf-parser to process MP4 files. Check if the OpenMP4Source function is called in any code that handles video files.Affected if The OpenMP4Source function in GPMF_mp4reader.c is used to parse MP4 files from any source
-
Assess file input sourceReview configuration or logs to identify whether the system processes MP4 files from untrusted or external sources. Check if user-uploaded, network-received, or third-party MP4 files are being parsed.Affected if The system processes MP4 files from untrusted or external sources using the vulnerable gpmf-parser version
You are affected if gpmf-parser version 1.2.1 is installed and the OpenMP4Source function is used to parse MP4 files, especially from untrusted sources.
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 dataUpdate to a patched version of gpmf-parser if available; otherwise, implement proper bounds checking in the OpenMP4Source function and validate MP4 file structure before processing. Consider sandboxing or restricting processing of untrusted MP4 files until a fix is deployed.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18699 — 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-18699 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