CVE-2024-34477

Fogproject privilege escalation

7.8 HIGHPublic exploitEPSS 0.27%

Published27 May 2024

Description

configureNFS in lib/common/functions.sh in FOG through 1.5.10 allows local users to gain privileges by mounting a crafted NFS share (because of no_root_squash and insecure). In order to exploit the vulnerability, someone needs to mount an NFS share in order to add an executable file as root. In addition, the SUID bit must be added to this file.

CVSS 3.1 breakdown

Attack vectorLocal

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Fogproject< 1.5.10.41

Remediation

Fixed in

Fogproject≥ 1.5.10.41

Patch & vendor advisories

https://forums.fogproject.org/topic/17486/fog-1-5-10-and-earlier-nfs-privilege-escalation-vulnerability

References

https://blog.hackvens.fr/advisories/CVE-2024-34477-Fogproject.htmlExploitThird Party Advisory
https://forums.fogproject.org/topic/17486/fog-1-5-10-and-earlier-nfs-privilege-escalation-vulnerabilityExploitVendor Advisory
https://github.com/FOGProject/fogproject/blob/a4bb1bf39ac53c3cbe623576915fbc3b5c80a00f/lib/common/functions.sh#L1360Product

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2024-34477 being actively exploited?

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

How severe is CVE-2024-34477?

CVE-2024-34477 has a CVSS 3.1 base score of 7.8, rated high. EPSS estimates a 0.27% probability of exploitation.

Which products are affected by CVE-2024-34477?

Affected products include Fogproject.

How do I fix CVE-2024-34477?

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

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2024-34477 against the real software inventory on every managed device, every day. 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

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.