CVE-2024-8038

CVE-2024-8038 is a high-severity vulnerability in Canonical Juju with a CVSS 3.x base score of 7.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-420.

Key facts

Description

Vulnerable juju introspection abstract UNIX domain socket. An abstract UNIX domain socket responsible for introspection is available without authentication locally to network namespace users. This enables denial of service attacks.

Frequently asked questions

What is CVE-2024-8038?
Vulnerable juju introspection abstract UNIX domain socket. An abstract UNIX domain socket responsible for introspection is available without authentication locally to network namespace users. This enables denial of service attacks.
How severe is CVE-2024-8038?
CVE-2024-8038 has a CVSS 3.x base score of 7.9, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability high.
Is CVE-2024-8038 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (11th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-8038?
CVE-2024-8038 affects Canonical Juju. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2024-8038?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2024-8038 have an EU (EUVD) identifier?
Yes. CVE-2024-8038 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-3173.
When was CVE-2024-8038 published?
CVE-2024-8038 was published on 2024-10-02 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Canonical Juju

All CVEs affecting Canonical Juju →

Other CWE-420 vulnerabilities

Browse all CWE-420 vulnerabilities →