CVE-2013-0651
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 Portal installation process in GE Intelligent Platforms Proficy Real-Time Information Portal stores sensitive information under the web root with insufficient access control, which allows remote attackers to read configuration files, and discover data-source credentials, via a direct 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 confidenceGE Proficy Real-Time Information Portal's installation process stores sensitive configuration files containing data-source credentials in directories accessible via the web server (under the web root). Without proper access controls, remote attackers can directly request these files via HTTP and obtain plaintext credentials for backend databases.
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.
-
Identify if GE Proficy Real-Time Information Portal is installedCheck for the presence of the portal installation directory, typically found under the GE installation path such as C:\Program Files\GE Digital\Proficy Real-Time Information Portal or similar locations depending on installation choicesAffected if The portal software is present on the system
-
Locate the web root directory used by the portalIdentify the web server configuration (IIS or built-in web server) and determine the document root where HTTP requests are served. Look in the portal configuration for the web root path settingAffected if A web root directory exists and is configured to serve HTTP requests
-
Search for configuration files containing credentials in the web rootExamine the web root directory and its subdirectories for configuration files (such as config.xml, connectionstrings.config, database.config, or similar naming patterns) that may contain data-source credentials or plaintext passwordsAffected if Sensitive configuration files exist within or under the web root directory
-
Verify HTTP accessibility of credential-containing filesUsing a web browser or HTTP client, attempt to directly request the suspected configuration files via HTTP (for example: http://yourportal/ config/configurationfile.xml). Check if the server returns the file contents without authenticationAffected if The configuration files containing credentials are directly accessible via HTTP without requiring authentication
-
Confirm plaintext credentials in accessed filesIf files are accessible, open them and verify whether they contain plaintext database usernames and passwords or other sensitive authentication credentialsAffected if The configuration files contain plaintext credentials for backend databases
If GE Proficy Real-Time Information Portal is installed and sensitive configuration files containing plaintext database credentials are stored within or accessible via the web root directory, the environment is vulnerable to CVE-2013-0651.
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 dataRelocate sensitive configuration files outside the web root directory and implement proper file-system access controls to prevent unauthorized web-accessible downloads of sensitive data.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0651 — 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-0651 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