What is CVE-2018-1129?A medium-severity flaw in Ceph, explained.
CVE-2018-1129 is a medium-severity flaw (CVSS 6.5) in Ceph, published on 10 July 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.9%. If you run an affected version, plan in the vendor’s fix.
Published 10 July 2018. Record last updated 29 August 2019. We keep this page's data up to date.
What is CVE-2018-1129? In plain terms.
An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can change data.
A flaw was found in the way signature calculation was handled by cephx authentication protocol. An attacker having access to ceph cluster network who is able to alter the message payload was able to bypass signature checks done by cephx protocol. Ceph branches master, mimic, luminous and jewel are believed to be vulnerable.
What kind of flaw is it?
- CWE-284Improper Access Control
- CWE-287Improper Authentication
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beOn the same local network
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan change data
Severity vector: CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Is CVE-2018-1129 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.9%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2018-1129 scores 25. Action: Monitor.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2018-1129 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2018-1129? 10 products.
The published record lists 10 products from 4 vendors. If you run one of these, check your version, then go to the fix below.
- Application
Ceph
by Ceph
Affected versions10.2.010.2.110.2.210.2.310.2.410.2.510.2.610.2.710.2.810.2.910.2.1010.2.1112.2.012.2.1 - Application
Ceph Storage
by Red Hat
Affected versions1.33 - Application
Ceph Storage Mon
by Red Hat
Affected versions23 - Application
Ceph Storage Osd
by Red Hat
Affected versions23 - Operating system
Debian Linux
by Debian
Affected versions8.09.0 - Operating system
Enterprise Linux
by Red Hat
Affected versions7.0 - Operating system
Enterprise Linux Desktop
by Red Hat
Affected versions7.0 - Operating system
Enterprise Linux Server
by Red Hat
Affected versions7.0 - Operating system
Enterprise Linux Workstation
by Red Hat
Affected versions7.0
How do I fix CVE-2018-1129? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
11 links- Show Bug.cgi (opens in a new tab)redhat.com
- ceph/ceph commit (opens in a new tab)github.com
- Issues (opens in a new tab)ceph.com
- Msg00100 (opens in a new tab)opensuse.org · 2019
- Kernel Live Patch Security Notice LSN 0054 1 (opens in a new tab)packetstormsecurity.com
- RHSA 2018:2177 (opens in a new tab)redhat.com
Does CVE-2018-1129 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A flaw was found in the way signature calculation was handled by cephx authentication protocol. An attacker having access to ceph cluster network who is able...
- Matched to
- Ceph on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2018-1129 is a medium-severity flaw in Ceph, published on 10 July 2018. An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can change data.
It scores 6.5 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2018-1129 is 25 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.9%. That can change at any time, which is why we keep watching.
For Ceph: 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 10.2.5 and 16 more. The record lists 10 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.