PT-2020-6419

Name of the Vulnerable Software and Affected Versions JerryScript version 2.2.0 Description The issue is related to an assertion in the parser parse object initializer function in the js-parser-expr.c component of the JerryScript JavaScript engine for the Internet of Things. This assertion is...

CVE-2020-13830

An issue was discovered on Samsung mobile devices with P9.0 software. One UI HOME logging can leak information. The Samsung ID is SVE-2019-16382 June 2020...

CVE-2020-13834

An issue was discovered on Samsung mobile devices with O8.x, P9.0, and Q10.0 with TEEGRIS software. Secure Folder does not properly restrict use of Android Debug Bridge adb for arbitrary installations. The Samsung ID is SVE-2020-17369 June 2020...

Information disclosure

An issue was discovered on Samsung mobile devices with P9.0 software. One UI HOME logging can leak information. The Samsung ID is SVE-2019-16382 June 2020...

CVE-2020-13830

Technical details are not publicly available in the provided documents. Monitor for updates from official sources.

CVE-2020-13836

CVE-2020-13836 affects Samsung mobile devices running O(8.x), P(9.0), and Q(10.0). A path traversal vulnerability exists in the HWRResProvider that can lead to data exposure. This is documented across multiple sources (including NVD, Red Hat, CNVD, CVE lists) with the Samsung ID SVE-2020-16954. T...

CVE-2020-13838

CVE-2020-13838 affects Samsung mobile devices running P (9.0) and Q (10.0) software, where the DeX Lockscreen fails to block access to the Quick Panel and notifications. The issue is documented across multiple sources (NVD entry and Red Hat advisory) without details on a concrete exploit vector o...

CVE-2020-13836: Improper Limitation of a Pathname to a Restricted Directory

An issue was discovered on Samsung mobile devices with O8.x, P9.0, and Q10.0 software. HWRResProvider allows path traversal for data exposure. The Samsung ID is SVE-2020-16954 June 2020...

CVE-2020-13829: Undefined Security Weakness

An issue was discovered on Samsung mobile devices with P9.0 and Q10.0 software. Attackers can disable the SEAndroid protection mechanism in the RKP. The Samsung ID is SVE-2019-15998 June 2020...

CVE-2020-13833: Improper Link Resolution Before File Access

An issue was discovered on Samsung mobile devices with O8.x, P9.0, and Q10.0 software. The system area allows arbitrary file overwrites via a symlink attack. The Samsung ID is SVE-2020-17183 June 2020...

CVE-2020-13831: Improper Restriction of Operations within the Bounds of a Memory Buffer

An issue was discovered on Samsung mobile devices with O8.x and P9.0 Exynos 7570 chipsets software. The Trustonic Kinibi component allows arbitrary memory mapping. The Samsung ID is SVE-2019-16665 June 2020...

CVE-2020-13830: Insertion of Sensitive Information into Log File

An issue was discovered on Samsung mobile devices with P9.0 software. One UI HOME logging can leak information. The Samsung ID is SVE-2019-16382 June 2020...

Improper Signature Verification

fastecdsa does not properly perform signature verification. When Elliptic Curve Digital Signature Algorithm ECDSA signature is used with NIST P-256 SHA-256, it does not properly handled the point at infinity, leading to a failure in the signature verification if an extreme value in k and s^-1 is...

CVE-2020-12607

An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a...

CVE-2020-12607

An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a...

PYSEC-2020-42

An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a...

Code injection

An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a...

CVE-2020-12607

An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a...

CVE-2020-12607

CVE-2020-12607 affects the fastecdsa library prior to 2.1.2, where using the NIST P-256 curve in the ECDSA implementation mishandles the point at infinity during signature verification. This can cause verification to fail for an otherwise valid signature when extreme values occur for k and s^-1, ...

CVE-2020-12607

An issue was discovered in fastecdsa before 2.1.2. When using the NIST P-256 curve in the ECDSA implementation, the point at infinity is mishandled. This means that for an extreme value in k and s^-1, the signature verification fails even if the signature is correct. This behavior is not solely a...