CVE-2018-1192
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 · uneditedIn Cloud Foundry Foundation cf-release versions prior to v285; cf-deployment versions prior to v1.7; UAA 4.5.x versions prior to 4.5.5, 4.8.x versions prior to 4.8.3, and 4.7.x versions prior to 4.7.4; and UAA-release 45.7.x versions prior to 45.7, 52.7.x versions prior to 52.7, and 53.3.x versions prior to 53.3, the SessionID is logged in audit event logs. An attacker can use the SessionID to impersonate a logged-in user.
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 confidenceThe UAA (User Account and Authentication) component in Cloud Foundry logs SessionIDs in audit event logs. An attacker with access to these logs can extract valid session identifiers and use them to impersonate authenticated users, enabling session hijacking attacks.
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>= 4.5.0, < 4.5.5>= 4.7.0, < 4.7.4>= 4.8.0, < 4.8.3= 45.7= 52.7= 53.3< 285< 1.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Check UAA versionRetrieve the installed UAA version by querying the UAA API endpoint /info or checking the UAA release manifest. Common command: cf curl /uaa/info or inspect the UAA deployment manifest.Affected if The version falls within >= 4.5.0 and < 4.5.5, >= 4.7.0 and < 4.7.4, or >= 4.8.0 and < 4.8.3.
-
Check UAA Release versionInspect the UAA Release version in the Cloud Foundry deployment. Check the release manifest or use: bosh releases | grep uaarelease or equivalent command for your deployment.Affected if The UAA Release version equals exactly 45.7, 52.7, or 53.3.
-
Check CF Release versionQuery the Cloud Foundry release version. Use: cf version or bosh releases | grep cf-release.Affected if The CF Release version is less than 285.
-
Check CF Deployment versionVerify the Cloud Foundry Deployment version. Use: bosh deployments or check the deployment manifest file.Affected if The CF Deployment version is less than 1.7.
-
Inspect audit logs for SessionIDsExamine the UAA audit event logs for the presence of session identifiers. Navigate to the log location (typically /var/vcap/sys/log/uaa or via the logging subsystem) and search for patterns containing 'session' or session token formats in the audit records.Affected if Audit logs contain session identifiers, session tokens, or session IDs in the event records.
You are affected if your UAA version is within the vulnerable ranges AND audit logging is enabled, resulting in session identifiers being written to logs.
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 data1.74.5.54.7.4
Upgrade UAA to version 4.5.5+, 4.7.4+, or 4.8.3+ (or corresponding UAA-release versions 45.7+, 52.7+, 53.3+) and verify that session identifiers are no longer written to audit logs.
- Consultation2.0 h
- Implementation4.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,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1192 — 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-2018-1192 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