CVE-2018-1191
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 · uneditedCloud Foundry Garden-runC, versions prior to 1.11.0, contains an information exposure vulnerability. A user with access to Garden logs may be able to obtain leaked credentials and perform authenticated actions using those credentials.
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 confidenceCloud Foundry Garden-runC versions prior to 1.11.0 contain an information exposure vulnerability where credentials are being written to Garden log files. Users with access to these logs can retrieve the leaked credentials and perform authenticated actions using them.
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< 1.9.0< 1.11.0CVSS 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 Garden-runC versionQuery your BOSH deployment for the garden-runc release version using 'bosh -e <environment> -d <deployment> vms' and inspect the release information, or check the garden-runc release manifestAffected if The installed garden-runc release version is earlier than 1.11.0
-
Check Cf Deployment versionQuery your BOSH deployment for the cf deployment version using 'bosh -e <environment> -d cf deployments' or inspect the cf-deployment manifestAffected if The installed cf-deployment version is earlier than 1.9.0
-
Locate Garden log filesIdentify Garden container logs directory in your deployment - typically found in the garden-runc job's log path or the Diego cell's filesystem where container stdout/stderr are writtenAffected if Garden log files exist and are accessible to users beyond the intended audience
-
Search logs for credential patternsGrep or search Garden log files for patterns matching credentials, API tokens, passwords, or secrets that may have been passed to containers during container creationAffected if Log files contain plaintext credentials, API tokens, or secrets that should not be exposed
You are affected if your Garden-runC version is below 1.11.0 or your Cf Deployment is below 1.9.0, and Garden log files exist and may contain exposed credentials.
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.9.01.11.0
Upgrade Garden-runC to version 1.11.0 or later. Additionally, rotate any credentials that may have been exposed in logs and restrict access to Garden log files to prevent further exposure.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1191 — 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-1191 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