CVE-2013-0652
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 · uneditedGE Intelligent Platforms Proficy Real-Time Information Portal does not restrict access to methods of an unspecified Java class, which allows remote attackers to obtain a username listing via an RMI call.
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 confidenceGE Intelligent Platforms Proficy Real-Time Information Portal has an access control weakness in its RMI (Remote Method Invocation) interface. The application fails to restrict access to certain methods of a Java class, allowing unauthenticated remote attackers to invoke these methods via RMI to retrieve a listing of usernames on the system.
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 dataall versions= 2.6= 3.0= 3.5CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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.
-
Confirm GE Proficy Real-Time Information Portal installationLook for the application in standard installation directories (e.g., C:\Program Files\GE Digital\Proficy Real-Time Information Portal) or check for the service named 'ProficyRIP' or similar in Windows Services or running processes.Affected if The application is installed and running on the system.
-
Identify installed versionCheck the application version by inspecting the installed software details, the about dialog within the application, or version files in the installation directory.Affected if The installed version matches 2.6, 3.0, 3.5, or falls within 'all versions' range.
-
Verify RMI service is exposedCheck if the Java RMI service is running, typically on default port 1099 or a configured RMI port. Use 'netstat -an' or similar network tools to identify listening RMI ports associated with the application.Affected if RMI port is open and listening on the system.
-
Assess network accessibility of RMI interfaceDetermine if the RMI port is accessible from untrusted network segments. Check firewall rules and network configuration to see if the RMI port accepts connections from non-localhost addresses or external IPs.Affected if RMI port is accessible from untrusted networks or external systems without authentication requirements.
A user is affected if GE Proficy Real-Time Information Portal is installed with an exposed RMI interface accessible from untrusted networks, allowing unauthenticated remote method invocation.
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 dataRestrict RMI access to trusted network segments or implement authentication/authorization controls on the exposed Java class methods. Consider firewall rules to block unauthorized RMI access from external networks.
- 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-2013-0652 — 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-2013-0652 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