CVE-2012-2267
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 · uneditedmaster.exe in the SNMP Master Agent in RealNetworks Helix Server and Helix Mobile Server 14.x before 14.3.x allows remote attackers to cause a denial of service (daemon crash) by establishing and closing a port-705 TCP connection, a different vulnerability than CVE-2012-1923.
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 confidenceThe SNMP Master Agent (master.exe) in RealNetworks Helix Server and Helix Mobile Server versions 14.x before 14.3.x contains a vulnerability where establishing and then closing a TCP connection to port 705 triggers a daemon crash. This indicates a flaw in the SNMP Master Agent's handling of connection state transitions, likely an unhandled exception or NULL pointer dereference when processing rapid connection open/close sequences.
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= 14.0.0= 14.0.1= 14.2= 14.2.0.212= 14.0.0= 14.0.1CVSS 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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 the installed Helix Server or Helix Mobile Server versionCheck the version through the admin web interface, or examine the server binaries/logs for version information, typically found in server startup logs or the binary file properties of master.exeAffected if The installed version is 14.0.0, 14.0.1, 14.2, or 14.2.0.212 for Helix Server; or 14.0.0 or 14.0.1 for Helix Mobile Server
-
Verify the SNMP Master Agent is enabled and listeningCheck if port 705 is open and listening on the server using netstat or a port scanner, or check the SNMP configuration in the server admin interfaceAffected if The SNMP Master Agent is enabled and port 705 is accessible, making the service exposed to the crash condition
-
Confirm the server is reachable on port 705Attempt a TCP connection to port 705 from a trusted source using telnet, nc, or PowerShell Test-NetConnection, then immediately close the connectionAffected if The port is open and accepting connections, which would trigger the crash vulnerability when the connection is opened and then closed rapidly
You are affected if your Helix Server version is 14.0.0, 14.0.1, 14.2, or 14.2.0.212 (or Helix Mobile Server 14.0.0/14.0.1) AND the SNMP Master Agent is enabled and port 705 is accessible on your network.
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 Helix Server/Helix Mobile Server 14.3.x or later, which contains the fix for this vulnerability. If immediate upgrading is not feasible, implement network access controls to restrict port 705 to only trusted management IPs.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-2267 — 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-2267 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