dbcve.org
Data Loss Prevention Enforce\/detection ServersApplication · Symantec

CVE-2012-6277

HIGH · 7.8 CVSS v3.1 Published 2020-02-21
Fix available
A fix is available. Upgrade to 10.0.1 / 10.16 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Multiple unspecified vulnerabilities in Autonomy KeyView IDOL before 10.16, as used in Symantec Mail Security for Microsoft Exchange before 6.5.8, Symantec Mail Security for Domino before 8.1.1, Symantec Messaging Gateway before 10.0.1, Symantec Data Loss Prevention (DLP) before 11.6.1, IBM Notes 8.5.x, IBM Lotus Domino 8.5.x before 8.5.3 FP4, and other products, allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted file, related to "a number of underlying issues" in which "some of these cases demonstrated memory corruption with attacker-controlled input and could be exploited to run arbitrary code."

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 confidence

Multiple memory corruption vulnerabilities in Autonomy KeyView IDOL file parsing library (before 10.16) allow remote code execution or denial of service via crafted malicious files. The vulnerabilities are triggered during parsing of specially designed attachments or uploaded content, with attacker-controlled input leading to memory corruption.

MitigationUpgrade Autonomy KeyView IDOL to version 10.16 or later, or apply vendor-supplied patches to affected Symantec and IBM products that incorporate the vulnerable library.

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
Data Loss Prevention Enforce\/detection ServersApplication
Affected:>= 11.0, < 11.6.1
DominoApplication
Affected:>= 8.5.0, <= 8.5.3.6
NotesApplication
Affected:>= 8.5, <= 8.5.3
Data Loss Prevention EndpointApplication
Affected:>= 11.0, < 11.6.1
Mail SecurityApplication
Affected:<= 6.5.7<= 8.1.0= 6.5.7
Messaging GatewayApplication
Affected:>= 9.5, < 10.0.1
Autonomy Keyview IdolApplication
Affected:< 10.16

CVSS 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed product that uses KeyView IDOL
    Determine which Symantec or IBM product is installed (Symantec Data Loss Prevention, IBM Domino, IBM Notes, Symantec Mail Security, or Symantec Messaging Gateway). Check installed programs or run product-specific version commands.
    Affected if Any of the listed products (Symantec DLP, IBM Domino, IBM Notes, Symantec Mail Security, Symantec Messaging Gateway) is installed.
  2. Check the version of the installed product
    Use product-specific commands or check the product's about/version information. For Symantec products, check the Enforce server or Endpoint version. For IBM, check Domino or Notes version using 'domino -v' or the Notes client version info.
    Affected if The installed version falls within any of these ranges: Symantec DLP >= 11.0 and < 11.6.1; IBM Domino >= 8.5.0 and <= 8.5.3.6; IBM Notes >= 8.5 and <= 8.5.3; Symantec Mail Security <= 6.5.7 or <= 8.1.0; Symantec Messaging Gateway >= 9.5 and < 10.0.1.
  3. Verify if file parsing or attachment processing is enabled
    Check if the product is configured to process file attachments or uploaded content. This is typically enabled by default for content analysis, DLP scanning, or email filtering features.
    Affected if File parsing or attachment scanning features are enabled, as the vulnerability is triggered during parsing of specially crafted files.
  4. Confirm the KeyView IDOL library version if accessible
    If the KeyView IDOL library version is exposed in product documentation or can be queried through product support tools, check that it is < 10.16.
    Affected if The embedded KeyView IDOL library version is earlier than 10.16.

You are affected if you have any of the listed products (Symantec DLP, IBM Domino, IBM Notes, Symantec Mail Security, or Symantec Messaging Gateway) running a version within the affected ranges AND file parsing/attachment processing is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 10.0.1 / 10.16 / 11.6.1 or later
Fixed in 10.0.110.1611.6.1
Interim mitigation

Upgrade Autonomy KeyView IDOL to version 10.16 or later, or apply vendor-supplied patches to affected Symantec and IBM products that incorporate the vulnerable library.

Fix this in Data Loss Prevention Enforce\/detection Servers Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,580
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-6277 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-6277 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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