Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2023-30629 | First vendor Publication | 2023-04-24 |
Vendor | Cve | Last vendor Modification | 2023-08-02 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | |||
---|---|---|---|
Overall CVSS Score | 7.5 | ||
Base Score | 7.5 | Environmental Score | 7.5 |
impact SubScore | 3.6 | Temporal Score | 7.5 |
Exploitabality Sub Score | 3.9 | ||
Attack Vector | Network | Attack Complexity | Low |
Privileges Required | None | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | None |
Integrity Impact | High | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
Vyper is a Pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.1 through 0.3.7, the Vyper compiler generates the wrong bytecode. Any contract that uses the `raw_call` with `revert_on_failure=False` and `max_outsize=0` receives the wrong response from `raw_call`. Depending on the memory garbage, the result can be either `True` or `False`. A patch is available and, as of time of publication, anticipated to be part of Vyper 0.3.8. As a workaround, one may always put `max_outsize>0`. |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-30629 |
CWE : Common Weakness Enumeration
% | Id | Name |
---|---|---|
100 % | CWE-670 | Always-Incorrect Control Flow Implementation |
CPE : Common Platform Enumeration
Type | Description | Count |
---|---|---|
Application | 5 |
Sources (Detail)
Alert History
Date | Informations |
---|---|
2023-08-12 01:28:56 |
|
2023-08-03 21:28:09 |
|
2023-08-02 21:27:48 |
|
2023-05-05 00:27:22 |
|
2023-04-25 17:27:16 |
|
2023-04-25 05:27:19 |
|