CVE-2015-9259: Malicious File Upload
First published: Sat Mar 31 2018(Updated: )
In Docker Notary before 0.1, the checkRoot function in gotuf/client/client.go does not check expiry of root.json files, despite a comment stating that it does. Even if a user creates a new root.json file after a key compromise, an attacker can produce update files referring to an old root.json file.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Docker | <0.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2015-9259?
The severity of CVE-2015-9259 is classified as medium due to the potential for an attacker to refer to compromised root.json files.
How do I fix CVE-2015-9259?
To fix CVE-2015-9259, upgrade Docker Notary to version 0.1 or later, which includes improvements to the root.json file expiry checks.
What are the implications of CVE-2015-9259?
CVE-2015-9259 allows an attacker to create update files referencing old root.json files, which may result in the use of compromised keys.
Who is affected by CVE-2015-9259?
Users of Docker Notary versions prior to 0.1 are affected by CVE-2015-9259 and should take immediate action to upgrade.
Is there any workaround for CVE-2015-9259?
There are no known workarounds for CVE-2015-9259 other than updating to a patched version of Docker Notary.
- agent/references
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/last-modified-date
- agent/author
- agent/severity
- agent/description
- agent/event
- agent/type
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/docker
- canonical/docker