CVE-2012-4696
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 · uneditedBuffer overflow in Beijer ADP 6.5.0-180_R1967 and 6.5.1-186_R2942, and H-Designer 6.5.0 B180_R1967, allows local users to gain privileges by inserting a long string into a DLL 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 confidenceBuffer overflow vulnerability in Beijer ADP and H-Designer industrial automation software allows local privilege escalation by inserting a long string into a DLL file. The vulnerability affects specific versions (ADP 6.5.0-180_R1967, 6.5.1-186_R2942, and H-Designer 6.5.0 B180_R1967).
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= 6.5.0-180_r1967= 6.5.1-186_r2942= 6.5.0_b180_r1967CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/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.
-
Check if Beijer ADP is installedSearch for Beijer ADP installation directory in standard locations (Program Files, Program Files (x86)) or check Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for Beijer entriesAffected if Beijer ADP is found on the system
-
Determine installed version of Beijer ADPLocate the ADP executable (typically named ADP.exe or similar) and check its file properties for version information, or look for a version file in the installation directoryAffected if Version matches 6.5.0-180_R1967 or 6.5.1-186_R2942
-
Check if H-Designer is installedSearch for H-Designer installation directory in standard locations or check Windows registry under uninstall entries for H-DesignerAffected if H-Designer is found on the system
-
Determine installed version of H-DesignerLocate the H-Designer executable and check its file properties for version information, looking specifically for version string 6.5.0 B180_R1967Affected if Version matches 6.5.0 B180_R1967
-
Inspect DLL files in the software directoryExamine all DLL files in the Beijer ADP or H-Designer installation directory for unexpected modifications or unusually large file sizes that could indicate tampering with a long string payloadAffected if Any DLL file shows signs of unauthorized modification or unusual size
User is affected if either Beijer ADP version 6.5.0-180_R1967 or 6.5.1-186_R2942, or H-Designer version 6.5.0 B180_R1967 is installed on the system.
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 to patched versions of Beijer ADP and H-Designer; restrict file system permissions to prevent unauthorized DLL modification.
- Consultation4.0 h
- Implementation6.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4696 — 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-4696 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