CVE-2023-29581

yasm 1.3.0.55.g101bc has a segmentation violation in the function delete_Token at modules/preprocs/nasm/nasm-pp.c. NOTE: although a libyasm application could become unavailable if this were exploited, the vendor's position is that there is no security relevance because there is either supposed to be input validation before data reaches libyasm, or a sandbox in which the application runs.

CVSS v3 5.5 MEDIUM

5.5^/10

CVSS v3 : MEDIUM

Vector :

Exploitability : 1.8 / Impact : 3.6

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required NONE

User Interaction REQUIRED

Confidentiality Impact NONE

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References

Link	Resource
https://bugzilla.redhat.com/show_bug.cgi?id=2186333
https://github.com/yasm/yasm/blob/master/SECURITY.md
https://github.com/yasm/yasm/issues/216	Exploit Issue Tracking Third Party Advisory
https://github.com/z1r00/fuzz_vuln/blob/main/yasm/segv/delete_Token/readme.md	Exploit Third Party Advisory

Configurations

Configuration 1 (hide)

cpe:2.3:a:yasm_project:yasm:1.3.0.55.g101bc:*:*:*:*:*:*:*

History

22 Mar 2024, 15:15

Type	Values Removed	Values Added
Summary	~~(en) yasm 1.3.0.55.g101bc was discovered to contain a segmentation violation via the function delete_Token at /nasm/nasm-pp.c.~~	(en) yasm 1.3.0.55.g101bc has a segmentation violation in the function delete_Token at modules/preprocs/nasm/nasm-pp.c. NOTE: although a libyasm application could become unavailable if this were exploited, the vendor's position is that there is no security relevance because there is either supposed to be input validation before data reaches libyasm, or a sandbox in which the application runs.
References		() https://bugzilla.redhat.com/show_bug.cgi?id=2186333 - () https://github.com/yasm/yasm/blob/master/SECURITY.md -

Information

Published : 2023-04-12 16:15

Updated : 2024-08-02 15:15

NVD link : CVE-2023-29581

Mitre link : CVE-2023-29581

CVE.ORG link : CVE-2023-29581

JSON object : View

Products Affected

yasm_project

yasm

CWE

NVD-CWE-noinfo

{"id": "CVE-2023-29581", "cveTags": [{"tags": ["disputed"], "sourceIdentifier": "cve@mitre.org"}], "metrics": {"cvssMetricV31": [{"type": "Primary", "source": "nvd@nist.gov", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.5, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 1.8}, {"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 5.5, "attackVector": "LOCAL", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 1.8}]}, "published": "2023-04-12T16:15:19.603", "references": [{"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2186333", "source": "cve@mitre.org"}, {"url": "https://github.com/yasm/yasm/blob/master/SECURITY.md", "source": "cve@mitre.org"}, {"url": "https://github.com/yasm/yasm/issues/216", "tags": ["Exploit", "Issue Tracking", "Third Party Advisory"], "source": "cve@mitre.org"}, {"url": "https://github.com/z1r00/fuzz_vuln/blob/main/yasm/segv/delete_Token/readme.md", "tags": ["Exploit", "Third Party Advisory"], "source": "cve@mitre.org"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Primary", "source": "nvd@nist.gov", "description": [{"lang": "en", "value": "NVD-CWE-noinfo"}]}], "descriptions": [{"lang": "en", "value": "yasm 1.3.0.55.g101bc has a segmentation violation in the function delete_Token at modules/preprocs/nasm/nasm-pp.c. NOTE: although a libyasm application could become unavailable if this were exploited, the vendor's position is that there is no security relevance because there is either supposed to be input validation before data reaches libyasm, or a sandbox in which the application runs."}], "lastModified": "2024-08-02T15:15:28.660", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:yasm_project:yasm:1.3.0.55.g101bc:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "4A03B4FD-736D-40B7-87B0-AC4EF2660C4B"}], "operator": "OR"}]}], "sourceIdentifier": "cve@mitre.org"}