LLVM before 18.1.3 generates code in which the LR register can be overwritten without data being saved to the stack, and thus there can sometimes be an exploitable error in the flow of control. This affects the ARM backend and can be demonstrated with Clang. NOTE: the vendor perspective is "we don't have strong objections for a CVE to be created ... It does seem that the likelihood of this miscompile enabling an exploit remains very low, because the miscompile resulting in this JOP gadget is such that the function is most likely to crash on most valid inputs to the function. So, if this function is covered by any testing, the miscompile is most likely to be discovered before the binary is shipped to production."

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - LLVM before 18.1.3 generates code in which the LR register can be overwritten without data being saved to
    the stack, and thus there can sometimes be an exploitable error in the flow of control. This affects the
    ARM backend and can be demonstrated with Clang. NOTE: the vendor perspective is "we don't have strong
    objections for a CVE to be created ... It does seem that the likelihood of this miscompile enabling an
    exploit remains very low, because the miscompile resulting in this JOP gadget is such that the function is
    most likely to crash on most valid inputs to the function. So, if this function is covered by any testing,
    the miscompile is most likely to be discovered before the binary is shipped to production."
    (CVE-2024-31852)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - LLVM before 18.1.3 generates code in which the LR register can be overwritten without data being saved to     the stack, and thus there can sometimes be an exploitable error in the flow of control. This affects the     ARM backend and can be demonstrated with Clang. NOTE: the vendor perspective is we don't have strong     objections for a CVE to be created ... It does seem that the likelihood of this miscompile enabling an     exploit remains very low, because the miscompile resulting in this JOP gadget is such that the function is     most likely to crash on most valid inputs to the function. So, if this function is covered by any testing,     the miscompile is most likely to be discovered before the binary is shipped to production.
    (CVE-2024-31852)

Note that Nessus relies on the presence of the package as reported by the vendor.

The version of libcxx / llvm / rust installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-31852 advisory.

  - LLVM before 18.1.3 generates code in which the LR register can be overwritten without data being saved to     the stack, and thus there can sometimes be an exploitable error in the flow of control. This affects the     ARM backend and can be demonstrated with Clang. NOTE: the vendor perspective is we don't have strong     objections for a CVE to be created ... It does seem that the likelihood of this miscompile enabling an     exploit remains very low, because the miscompile resulting in this JOP gadget is such that the function is     most likely to crash on most valid inputs to the function. So, if this function is covered by any testing,     the miscompile is most likely to be discovered before the binary is shipped to production.
    (CVE-2024-31852)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The version of libcxx / llvm / rust installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-31852 advisory.

  - LLVM before 18.1.3 generates code in which the LR register can be overwritten without data being saved to     the stack, and thus there can sometimes be an exploitable error in the flow of control. This affects the     ARM backend and can be demonstrated with Clang. NOTE: the vendor perspective is we don't have strong     objections for a CVE to be created ... It does seem that the likelihood of this miscompile enabling an     exploit remains very low, because the miscompile resulting in this JOP gadget is such that the function is     most likely to crash on most valid inputs to the function. So, if this function is covered by any testing,     the miscompile is most likely to be discovered before the binary is shipped to production.
    (CVE-2024-31852)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
457831	Echo: llvm-toolchain-17: security update to 1:17.0.6-22+e1	Tenable Cloud Security	Echo Local Security Checks	Local	medium
457831	Echo: llvm-toolchain-17: security update to 1:17.0.6-22+e1	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	medium
244962	Linux Distros Unpatched Vulnerability : CVE-2024-31852	Nessus	Misc.	Local	medium
215439	Azure Linux 3.0 Security Update: libcxx / llvm / rust (CVE-2024-31852)	Nessus	Azure Linux Local Security Checks	Local	medium
205781	CBL Mariner 2.0 Security Update: libcxx / llvm / rust (CVE-2024-31852)	Nessus	MarinerOS Local Security Checks	Local	medium

Detections

Analytics

CVE-2024-31852

medium

Tenable Plugins

medium

medium

medium

medium

medium