CVE-2008-0174
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 Fanuc Proficy Real-Time Information Portal 2.6 and earlier uses HTTP Basic Authentication, which transmits usernames and passwords in base64-encoded cleartext and allows remote attackers to steal the passwords and gain privileges.
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 Fanuc Proficy Real-Time Information Portal 2.6 and earlier uses HTTP Basic Authentication, which transmits usernames and passwords in base64-encoded format. While base64 is not encryption, it obscures credentials from casual observation; however, anyone intercepting the HTTP traffic can trivially decode the base64 string to obtain plaintext passwords, enabling remote attackers to hijack user accounts and gain unauthorized system access.
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<= 2.6CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 Fanuc Proficy Real-Time Information Portal is installedLocate the installation directory or check system inventory for the Proficy Real-Time Information Portal application. Common installation paths may include Program Files/GE Fanuc or similar. Use system inventory tools if available.Affected if The application is found on the system and is version 2.6 or earlier
-
Determine the installed version of the softwareCheck the application version through the software itself (typically accessible via Help > About in the application), or check version information in the installation directory. Compare the version number against the affected range of 2.6 and earlier.Affected if The installed version is 2.6 or any earlier version number
-
Verify HTTP Basic Authentication is in useInspect the web server configuration or authentication settings within the Proficy Real-Time Information Portal admin interface. Check if the authentication method is explicitly set to HTTP Basic Authentication or if the login prompt appears to use standard browser basic auth dialogs.Affected if HTTP Basic Authentication is enabled and configured as the authentication mechanism
-
Confirm the web interface is not using TLS encryptionExamine the protocol used to access the portal URL. Check if the connection uses HTTP instead of HTTPS, or verify the server configuration for SSL/TLS settings. A URL starting with http:// rather than https:// indicates unencrypted access.Affected if The portal is accessible over unencrypted HTTP without TLS/SSL protection
A system is affected if it runs GE Fanuc Proficy Real-Time Information Portal version 2.6 or earlier with HTTP Basic Authentication enabled over unencrypted HTTP connections.
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 a patched version of the software that implements secure authentication (such as digest authentication, form-based authentication with session tokens, or certificate-based auth) over TLS-encrypted channels. If no upgrade is available, network segmentation and restricting access to trusted networks may reduce exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0174 — 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-2008-0174 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