# What is CVE-2022-24769?

> CVE-2022-24769 is a medium-severity flaw (CVSS 5.9) in Moby from Mobyproject, published on 24 March 2022. 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 0.5%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2022-24769

## At a glance

- **Verdict:** Plan it in. No sign of exploitation and a low forecast. Patch it in your normal update cycle.
- **Precursor Intelligence risk score:** 22 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes.
- **Severity:** Medium (CVSS 5.9 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 0.5% (latest exploit-likelihood forecast)
- **Published:** 24 March 2022
- **Record last updated:** 31 January 2024
- **Main product:** Moby from Mobyproject
- **Affected products:** 5

## What is CVE-2022-24769? In plain terms

An attacker has to be already on the device without logging in, and nobody has to click anything. If it works, the attacker can read some data, change some data and slow it down.

### The official description

Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted. This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a workaround, the entry point of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting.

### What kind of flaw is it?

- CWE-732: Incorrect Permission Assignment for Critical Resource

### How an attack on it works

- Where an attacker can be: Already on the device
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can read some data, change some data and slow it down

Severity vector: `CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`

## Is CVE-2022-24769 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 0.5%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 0.5%, 0.5%, 0.5%, 0.5%, 0.5%, 0.5%, 0.5%.

### Timeline

- 24 March 2022: Published
- 31 January 2024: Record last updated

### How Precursor Intelligence ranks it

CVE-2022-24769 scores **22 out of 100 (Low)**, with the action "Monitor".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2022-24769?

The published record lists 5 products. Versions are as published: "before 20.10.14" means every version up to, but not including, 20.10.14.

- [Moby](https://www.precursorintelligence.com/product/mobyproject/moby) by [Mobyproject](https://www.precursorintelligence.com/vendors/mobyproject) (Application): before 20.10.14
- [Fedora](https://www.precursorintelligence.com/product/fedoraproject/fedora) by [Fedoraproject](https://www.precursorintelligence.com/vendors/fedoraproject) (Operating system): 34, 35, 36
- [Debian Linux](https://www.precursorintelligence.com/product/debian/debian_linux) by [Debian](https://www.precursorintelligence.com/vendors/debian) (Operating system): 11.0
- [Linux kernel](https://www.precursorintelligence.com/product/linux/linux_kernel) by [Linux](https://www.precursorintelligence.com/vendors/linux) (Operating system): version not specified
- [Runc](https://www.precursorintelligence.com/product/linuxfoundation/runc) by [Linuxfoundation](https://www.precursorintelligence.com/vendors/linuxfoundation) (Application): before 1.1.2

## How do I fix CVE-2022-24769?

1. **Check whether you run it.** Compare 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.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track 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

- [github.com](https://github.com/moby/moby/commit/2bbc786e4c59761d722d2d1518cd0a32829bc07f) (Patch, Third-party advisory)
- [github.com](https://github.com/moby/moby/security/advisories/GHSA-2mm7-x5h6-5pvq) (Mitigation, Third-party advisory)
- [openwall.com](http://www.openwall.com/lists/oss-security/2022/05/12/1) (Mailing list, Third-party advisory)
- [github.com](https://github.com/moby/moby/releases/tag/v20.10.14) (Release notes, Third-party advisory)
- [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6PMQKCAPK2AR3DCYITJYMMNBEGQBGLCC/)
- [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/A5AFKOQ5CE3CEIULWW4FLQKHFFU6FSYG/)
- [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/A5FQJ3MLFSEKQYCFPFZIKYGBXPZUJFVY/)
- [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FPOJUJZXGMIVKRS4QR75F6OIXNQ6LDBL/)
- [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HIMAHZ6AUIKN7AX26KHZYBXVECIOVWBH/)
- [lists.fedoraproject.org](https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HQCVS7WBFSTKJFNX5PGDRARMTOFWV2O7/)
- [security.gentoo.org](https://security.gentoo.org/glsa/202401-31)
- [debian.org](https://www.debian.org/security/2022/dsa-5162) (Third-party advisory)

## Questions

### What is CVE-2022-24769?

CVE-2022-24769 is a medium-severity flaw in Moby from Mobyproject, published on 24 March 2022. An attacker has to be already on the device without logging in, and nobody has to click anything. If it works, the attacker can read some data, change some data and slow it down.

### How serious is CVE-2022-24769?

It scores 5.9 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2022-24769 is 22 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.

### Is CVE-2022-24769 being exploited?

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 0.5%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2022-24769 affect?

For Moby from Mobyproject: before 20.10.14. The record lists 5 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2022-24769?

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.

## Does CVE-2022-24769 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact