Intelligent Platforms Proficy Plant ApplicationsApplication · Ge

CVE-2012-0230

HIGH · 10.0 CVSS v2.0 Published 2012-03-15
Fix available
A fix is available. Upgrade to after 5.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
PRRDS.exe in the Proficy Remote Data Service in GE Intelligent Platforms Proficy Plant Applications 5.0 and earlier allows remote attackers to cause a denial of service (memory corruption) or possibly execute arbitrary code via a crafted TCP session on port 12299.

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 confidence

PRRDS.exe in GE Intelligent Platforms Proficy Plant Applications 5.0 and earlier contains a memory corruption vulnerability when processing crafted TCP packets on port 12299, allowing remote unauthenticated attackers to cause denial of service or potentially achieve arbitrary code execution.

MitigationRestrict network access to port 12299 via firewall or network segmentation; apply vendor patch when available; if the service is not required in production, disable it.

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
Intelligent Platforms Proficy Plant ApplicationsApplication
Affected:<= 5.0= 4.2.2= 4.2.3= 4.3.1= 4.4.1= 215.8

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/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 checks

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

  1. Verify PRRDS.exe is present
    Locate the PRRDS.exe file on the system, typically found in the Proficy Plant Applications installation directory (e.g., C:\Program Files\GE Digital\Proficy Plant Applications\ or similar). Check if the process is running using Task Manager or command: tasklist /FI "IMAGENAME eq PRRDS.exe"
    Affected if PRRDS.exe exists and is running on the system - this is the vulnerable component
  2. Confirm port 12299 is listening
    Run command: netstat -an | findstr :12299 or use PowerShell: Get-NetTCPConnection -LocalPort 12299 -State Listen to check if the service is listening on TCP port 12299
    Affected if Port 12299 is open and listening - this is the attack vector for the vulnerability
  3. Determine installed Proficy Plant Applications version
    Check the installed version via Windows Programs and Features, or locate version information in the installation directory (look for version.xml, about dialog, or check file properties of main executables). Compare against affected versions: <= 5.0, 4.2.2, 4.2.3, 4.3.1, 4.4.1, 215.8
    Affected if Installed version matches or is older than the affected versions listed (4.2.2, 4.2.3, 4.3.1, 4.4.1, 215.8, or any version 5.0 and earlier)
  4. Assess network exposure of port 12299
    Verify if port 12299 is accessible from untrusted networks by reviewing firewall rules (Windows Firewall with Advanced Security, or network perimeter firewall). Check if the host is directly exposed to the internet or accessible from less-trusted network segments
    Affected if Port 12299 is accessible from untrusted network segments - the vulnerability is remotely exploitable without authentication

The environment is affected if PRRDS.exe is running, port 12299 is listening and exposed to untrusted networks, AND the installed Proficy Plant Applications version matches the affected version list.

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 a release after 5.0
Interim mitigation

Restrict network access to port 12299 via firewall or network segmentation; apply vendor patch when available; if the service is not required in production, disable it.

Fix this in Intelligent Platforms Proficy Plant Applications Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0230 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0230 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