CVE-2012-0268
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 · uneditedInteger overflow in the CYImage::LoadJPG method in YImage.dll in Yahoo! Messenger before 11.5.0.155, when photo sharing is enabled, might allow remote attackers to execute arbitrary code via a crafted JPG image that triggers a heap-based buffer overflow.
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 confidenceInteger overflow in the CYImage::LoadJPG method in YImage.dll in Yahoo! Messenger before 11.5.0.155 allows remote attackers to execute arbitrary code via a crafted JPG image when photo sharing is enabled, triggering a heap-based buffer overflow.
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<= 11.5.0.152= 0.99.17-1= 1.0= 1.0.4= 1.0.6= 2.0.1.4= 3.0= 3.0.1= 3.5= 4.0= 4.1= 5.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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/Au:N/C:P/I:P/A:P
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.
-
Check installed Yahoo! Messenger versionOpen Yahoo! Messenger, go to Help > About Yahoo! Messenger, or check the program's version through Windows Add/Remove Programs or the executable properties.Affected if The installed version is 11.5.0.152 or earlier, or matches one of these affected versions: 0.99.17-1, 1.0, 1.0.4, 1.0.6, 2.0.1.4, 3.0, 3.0.1, 3.5, 4.0, 4.1, or 5.0
-
Identify YImage.dll versionLocate YImage.dll in the Yahoo! Messenger installation directory (typically in the main program folder). Right-click the file, select Properties, and view the File Version information.Affected if The YImage.dll version corresponds to an unpatched Yahoo! Messenger installation (versions listed above) and is older than the version shipped with 11.5.0.155
-
Verify photo sharing is enabledIn Yahoo! Messenger, navigate to the photo sharing settings or preferences panel. Look for the photo sharing or photo upload feature configuration.Affected if Photo sharing is currently enabled, which is required to trigger the vulnerability when processing a crafted JPG image
You are affected if you are running any Yahoo! Messenger version listed as vulnerable (11.5.0.152 or earlier, or any of the specific versions 0.99.17-1 through 5.0) AND photo sharing is enabled.
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 Yahoo! Messenger to version 11.5.0.155 or later to obtain the patched YImage.dll; alternatively, disable the photo sharing feature as a workaround until the upgrade can be performed.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0268 — 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-0268 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