CVE-2012-1616
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 · uneditedUse-after-free vulnerability in icclib before 2.13, as used by Argyll CMS before 1.4 and possibly other programs, allows remote attackers to cause a denial of service (crash) or execute arbitrary code via a crafted ICC profile 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 · moderate confidenceUse-after-free vulnerability in icclib library versions before 2.13 allows remote attackers to execute arbitrary code or cause denial of service via a specially crafted ICC profile file. The vulnerability affects Argyll CMS before 1.4 and potentially other software that links against the vulnerable icclib versions.
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.3.7= 0.1.0= 0.2.0= 0.2.1= 0.2.2= 0.3.0= 0.6.0= 0.7.0= 1.0.0= 1.0.2= 1.0.3= 1.0.4<= 2.11= 1.23= 2.00= 2.02= 2.03CVSS 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.
-
Identify installed Argyll CMS versionRun 'argyllgamut -v' or check package manager for argyllcms versionAffected if Version is 1.3.7 or lower, or matches any of these: 0.1.0, 0.2.0, 0.2.1, 0.2.2, 0.3.0, 0.6.0, 0.7.0, 1.0.0, 1.0.2, 1.0.3, 1.0.4, or any version below 1.4.0
-
Identify installed icclib versionRun 'icclib -v' if available, or check shared library version via 'ldconfig -p | grep icclib' and examine the library file metadata, or check software that bundles icclibAffected if Version is 2.11 or lower, or matches: 1.23, 2.00, 2.02, or 2.03, or any version below 2.13
-
Determine if software processes ICC profile filesReview application logs, configuration, or usage patterns to see if ICC profile loading is a normal operation. Check for commands like 'collink', 'spotread', 'targen', or other Argyll tools that handle color profilesAffected if The software routinely loads, parses, or validates ICC profile files as part of normal operation
-
Verify ICC profile processing is enabledExamine application configuration files, command-line arguments, or environment variables that control ICC profile handling in your color management workflowAffected if ICC profile processing, parsing, or loading features are enabled or accessible to untrusted profile files
You are affected if you have Argyll CMS below version 1.4 or icclib below version 2.13 installed AND your system processes ICC profile files from untrusted or external 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.
dbcve · scopedUpgrade icclib to version 2.13 or later and Argyll CMS to 1.4 or later. As a defense-in-depth measure, implement strict validation of ICC profile files before processing.
Argyll CMS 1.4 (which includes icclib 2.13)
- Upgrade icclib to version 2.13 or later
- Upgrade Argyll CMS to version 1.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1616 — 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-1616 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