CVE-2012-4964
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 · uneditedThe Samsung printer firmware before 20121031 has a hardcoded read-write SNMP community, which makes it easier for remote attackers to obtain administrative access via an SNMP request.
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 confidenceSamsung printer firmware versions before 20121031 contain a hardcoded read-write SNMP community string that is shipped in the default configuration. This allows remote attackers who can send SNMP requests to the device to obtain full administrative access, as the hardcoded community string provides read-write privileges.
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<= 20121030CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Identify Samsung printer on networkLocate Samsung printer devices by checking network inventory, scanning for SNMP services on port 161/162, or identifying Samsung printer IP addresses in your environmentAffected if Any Samsung printer device exists on the network
-
Check printer firmware versionAccess the printer web interface (HTTP/HTTPS) and navigate to the Firmware Information or Status page, or query the printer via SNMP using snmpwalk on OID 1.3.6.1.4.1.236.11.5.1.1.1.1.1.0 for the firmware versionAffected if Firmware version displays as a date string earlier than 20121031, or is otherwise <= 20121030
-
Verify SNMP is enabledSend an SNMP GET request to the printer on UDP port 161 using a tool like snmpget or snmpwalk. Try using public or private community strings as test valuesAffected if SNMP service responds to requests, indicating SNMP is enabled on the device
-
Test default SNMP community stringQuery the printer using SNMP with community string 'public' or 'private' as the read-write community. Use snmpwalk with -c flag specifying these strings against OID 1.3.6.1.2.1.1 to verify read-write accessAffected if SNMP queries succeed with read-write privileges using the default community strings, confirming the hardcoded string is active
A Samsung printer with firmware version dated 20121030 or earlier that has SNMP enabled and responds to the default hardcoded community string is affected by this vulnerability.
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 dataUpdate Samsung printer firmware to a version released on or after 20121031, and change or disable the default SNMP community strings to unique, strong values.
- Consultation3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4964 — 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-4964 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