DockerApplication
CVE-2014-0048
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 · uneditedAn issue was found in Docker before 1.6.0. Some programs and scripts in Docker are downloaded via HTTP and then executed or used in unsafe ways.
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 confidenceDocker before version 1.6.0 downloaded programs and scripts over insecure HTTP connections, allowing man-in-the-middle attackers to inject malicious code during the download process. This affects bootstrap scripts and auxiliary components that Docker fetches during installation or operation.
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
DockerApplication
< 1.5.0
GeodeApplication
= 1.12.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
- 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.
-
Check installed Docker versionRun `docker --version` or `docker version` to obtain the Docker daemon version numberAffected if The version is less than 1.5.0 (e.g., 1.4.1, 1.3.x, etc.)
-
Check for Apache Geode versionRun `gfsh version` or inspect the geode-core JAR file metadata for version 1.12.0Affected if Apache Geode version is exactly 1.12.0
-
Identify automated script fetching in Docker operationsReview any Docker installation scripts, bootstrap scripts, or automation that pulls external programs or scripts during Docker setup or container initializationAffected if Scripts or programs are fetched over HTTP (not HTTPS) URLs and the Docker version is below 1.6.0
A system is affected if Docker version is below 1.5.0 or Apache Geode version equals 1.12.0, and either uses automated scripts fetched over insecure HTTP connections during installation or operation.
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.
dbcve · scoped1.5.0
Upgrade Docker to version 1.6.0 or later. For legacy systems that cannot upgrade immediately, verify all downloaded scripts through checksums or cryptographic signatures before execution.
Docker 1.6.0 or later (preferably latest stable 1.x or 2.x release)
- Backup all Docker data, containers, images, and volumes
- Stop the Docker daemon service
- Upgrade Docker to version 1.6.0 or later using your system's package manager (e.g., apt-get, yum, dnf)
- Verify the upgrade was successful by running 'docker --version'
- Start the Docker daemon service
- Test that containers can be created and run normally
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Docker
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0048 — 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-2014-0048 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