CVE-2024-1929: Rpm Dnf5 vulnerability (CVSS 7.5)

Description

Local Root Exploit via Configuration Dictionary in dnf5daemon-server before 5.1.17 allows a malicious user to impact Confidentiality and Integrity via Configuration Dictionary. There are issues with the D-Bus interface long before Polkit is invoked. The `org.rpm.dnf.v0.SessionManager.open_session` method takes a key/value map of configuration entries. A sub-entry in this map, placed under the "config" key, is another key/value map. The configuration values found in it will be forwarded as configuration overrides to the `libdnf5::Base` configuration. Practically all libdnf5 configuration aspects can be influenced here. Already when opening the session via D-Bus, the libdnf5 will be initialized using these override configuration values. There is no sanity checking of the content of this "config" map, which is untrusted data. It is possible to make the library loading a plug-in shared library under control of an unprivileged user, hence achieving root access.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityHigh

Privileges requiredLow

User interactionNone

ScopeChanged

ConfidentialityHigh

IntegrityHigh

AvailabilityNone

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N

Affected products

Rpm Dnf5< 5.1.17

Remediation

Fixed in

Rpm Dnf5≥ 5.1.17

References

https://www.openwall.com/lists/oss-security/2024/03/04/2ExploitMailing ListThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-1929 being actively exploited?

CVE-2024-1929 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.29%.

How severe is CVE-2024-1929?

CVE-2024-1929 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.29% probability of exploitation.

Which products are affected by CVE-2024-1929?

Affected products include Rpm Dnf5.

How do I fix CVE-2024-1929?

Upgrade affected software to a fixed version, for example Rpm Dnf5 5.1.17 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-1929 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo