CVE-2015-1817: Buffer Overflow
Published Aug 18, 2017
·Updated
Last updated 24 July 2024
Affected Software
15 affected componentsFixes available
debian/musl
1.2.2-11.2.3-11.2.5-1.1
Musl-libc Musl=0.9.15
Musl-libc Musl=1.0.0
Musl-libc Musl=1.0.1
Musl-libc Musl=1.0.2
Musl-libc Musl=1.0.3
Musl-libc Musl=1.0.4
Musl-libc Musl=1.1.0
Musl-libc Musl=1.1.1
Musl-libc Musl=1.1.2
Musl-libc Musl=1.1.3
Musl-libc Musl=1.1.4
Musl-libc Musl=1.1.5
Musl-libc Musl=1.1.6
Musl-libc Musl=1.1.7
Remediation
Patch Available
Event History
Aug 18, 2017
CVE Published
via MITRE·04:00 PM
Data Sourced
via MITRE·04:00 PM
Description
Aug 29, 2024
Data Sourced
via Launchpad·12:44 PM
Description
Sep 14, 2024
Data Sourced
via Ubuntu·12:45 PM
RemedyDescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2015-1817?
CVE-2015-1817 is classified as a high severity vulnerability due to its potential for stack-based buffer overflow exploits.
2
How do I fix CVE-2015-1817?
To fix CVE-2015-1817, upgrade to musl libc version 1.2.2-1 or later.
3
Which versions of musl libc are affected by CVE-2015-1817?
CVE-2015-1817 affects musl libc versions from 0.9.15 through 1.0.4, and 1.1.0 through 1.1.7.
4
Can CVE-2015-1817 be exploited remotely?
Yes, CVE-2015-1817 can potentially be exploited remotely, allowing attackers to impact runtime behavior.
5
What is the impact of CVE-2015-1817?
The impact of CVE-2015-1817 includes the risk of arbitrary code execution and denial of service due to the buffer overflow.