CVE-2012-1264
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 · uneditedUnspecified vulnerability in Gretech GOM Media Player before 2.1.37.5091 allows remote attackers to execute arbitrary code via a crafted AVI file.
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 confidenceBuffer overflow or memory corruption vulnerability in Gretech GOM Media Player's AVI file parsing code prior to version 2.1.37.5091 allows remote attackers to achieve arbitrary code execution by tricking users into opening specially crafted AVI files.
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.1.36.5083CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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.
-
Confirm GOM Media Player is installedCheck for GOM Player executable at common installation paths: C:\Program Files\GOM\GOM Player\GOM.exe or C:\Program Files (x86)\GOM\GOM Player\GOM.exe. Also check Start Menu for GOM Player entries.Affected if GOM Media Player executable is present on the system
-
Identify installed versionRight-click GOM.exe, select Properties, then view the Details tab for Product Version. Alternatively, right-click the executable, select Properties, and check the Version tab.Affected if Version displays as 2.1.36.5083 or earlier (any version <= 2.1.36.5083)
-
Verify vulnerable version rangeCompare the identified product version against the affected range. Versions 2.1.36.5083 and all prior versions are vulnerable.Affected if Installed version is 2.1.36.5083 or lower (anything before the fixed version 2.1.37.5091)
The system is affected if GOM Media Player is installed and the version is 2.1.36.5083 or any earlier version, as the vulnerability exists in AVI file parsing code prior to version 2.1.37.5091.
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.
dbcve · scopedUpgrade GOM Media Player to version 2.1.37.5091 or later; avoid opening untrusted AVI files from unknown or untrusted sources.
Gom Media Player 2.1.37.5091 or later
- Download Gom Media Player version 2.1.37.5091 or later from the official vendor website (gom.gomtv.com)
- Uninstall the current version of Gom Media Player
- Install the updated version (2.1.37.5091 or later)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1264 — 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-2012-1264 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