7542 matches found
PT-2024-18490 · Tvapi · Tvapi
Name of the Vulnerable Software and Affected Versions: TVAPI affected versions not specified Description: The issue is related to a possible out of bounds write in TVAPI due to a missing bounds check. This could lead to local escalation of privilege, with System execution privileges needed. User...
PT-2024-18501 · Mediatek +1 · Mt6580 +1
Name of the Vulnerable Software and Affected Versions: No specific software or versions are mentioned in the provided descriptions. Description: The issue is related to a missing bounds check in keyInstall, which could lead to an out of bounds write. This might result in local escalation of...
PT-2024-18499 · Unknown · Alac Decoder
Name of the Vulnerable Software and Affected Versions: alac decoder affected versions not specified Description: In the alac decoder, there is a possible information disclosure due to an incorrect bounds check. This could lead to remote code execution with no additional execution privileges neede...
PT-2024-18494 · Mediatek +3 · Mt2713 +7
Name of the Vulnerable Software and Affected Versions: In da affected versions not specified Description: The issue is related to a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interactio...
PT-2024-18489 · Tvapi · Tvapi
Name of the Vulnerable Software and Affected Versions: TVAPI affected versions not specified Description: The issue is related to a possible out of bounds write in TVAPI due to a missing bounds check. This could lead to local escalation of privilege, with System execution privileges needed. User...
Buffer Overflow
Vyper is vulnerable to Buffer Overflow Vulnerability. The vulnerability is due to the improper bounds check for slices because it does not account for the potential overflow of start + length when non-literal values are used. This issue can be exploited by an attacker to perform out of bounds...
GHSA-9X7F-GWXQ-6F2C Vyper's bounds check on built-in `slice()` function can be overflowed
Summary The bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice function uses a non-literal argument for the start or length variable, this creates the ability for an attacker to overflow the bounds check. This issue...
Vyper's bounds check on built-in `slice()` function can be overflowed
Summary The bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice function uses a non-literal argument for the start or length variable, this creates the ability for an attacker to overflow the bounds check. This issue...
CVE-2024-24561
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice function uses a non-literal argument for the start ...
Design/Logic Flaw
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice function uses a non-literal argument for the start ...
CVE-2024-24561 Vyper bounds check on built-in `slice()` function can be overflowed
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice function uses a non-literal argument for the start ...
CVE-2024-24561 Vyper bounds check on built-in `slice()` function can be overflowed
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice function uses a non-literal argument for the start ...
CVE-2024-24561 Vyper bounds check on built-in `slice()` function can be overflowed
Vyper is a pythonic Smart Contract Language for the ethereum virtual machine. In versions 0.3.10 and earlier, the bounds check for slices does not account for the ability for start + length to overflow when the values aren't literals. If a slice function uses a non-literal argument for the start ...
PUB-A-309407679
there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation...
glibc qsort() Out-Of-Bounds Read / Write Exploit
Qualys discovered a memory corruption in the glibc's qsort function, due to a missing bounds check. To be vulnerable, a program must call qsort with a nontransitive comparison function a function cmpint a, int b that returns a - b, for example and with a large number of attacker-controlled elemen...
USN-6616-1: OpenLDAP vulnerability
It was discovered that OpenLDAP was not properly performing bounds checks when executing functions related to LDAP URLs. An attacker could possibly use this issue to cause a denial of service...
CVE-2023-48356
In jpg driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service with System execution privileges needed...
CVE-2023-48355
In jpg driver, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service with System execution privileges needed...