vyperlang Vyper up to 0.3.10 risky encryption

Summaryinfo

A vulnerability classified as problematic has been found in vyperlang Vyper up to 0.3.10. This affects an unknown function. Performing a manipulation results in risky encryption. This vulnerability is cataloged as CVE-2024-24559. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in vyperlang Vyper up to 0.3.10. This affects some unknown processing. The manipulation with an unknown input leads to a risky encryption vulnerability. CWE is classifying the issue as CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. This is going to have an impact on confidentiality. The summary by CVE is:

Vyper is a Pythonic Smart Contract Language for the EVM. There is an error in the stack management when compiling the `IR` for `sha3_64`. Concretely, the `height` variable is miscalculated. The vulnerability can't be triggered without writing the `IR` by hand (that is, it cannot be triggered from regular vyper code). `sha3_64` is used for retrieval in mappings. No flow that would cache the `key` was found so the issue shouldn't be possible to trigger when compiling the compiler-generated `IR`. This issue isn't triggered during normal compilation of vyper code so the impact is low. At the time of publication there is no patch available.

The weakness was shared 02/06/2024 as GHSA-6845-xw22-ffxv. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-24559 since 01/25/2024. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

The exploit is shared for download at github.com. It is declared as proof-of-concept.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• vyperlang

Name

• Vyper

Version

• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6
• 0.3.7
• 0.3.8
• 0.3.9
• 0.3.10

Website

• Product: https://github.com/vyperlang/vyper/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion