CVE-2013-1591: Buffer Overflow
Stack-based buffer overflow in libpixman, as used in Pale Moon before 15.4 and possibly other products, has unspecified impact and context-dependent attack vectors. NOTE: this issue might be resultant from an integer overflow in the fastcompositescaledbilinear function in pixman-inlines.h, which triggers an infinite loop.
Other sources
Stack-based buffer overflow in libpixman, as used in Pale Moon before 15.4, has unspecified impact and attack vectors.
The upstream commit to correct this flaw:
http://cgit.freedesktop.org/pixman/commit/?id=de60e2e0e3eb6084f8f14b63f25b3cbfb012943f
The affected code (pixman/pixman-inlines.h, fastcompositescaledbilinear()) is present in the version of pixmap shipped with Fedora 17 (0.24.4), but is not present in Red Hat Enterprise Linux 5 or 6 (the fastcompositescaledbilinear() function is in pixman/pixman-fast-path.h, but the vulnerable code is not there and I don't detect anything comparable). So it's likely that the vulnerable code was introduced after 0.22.0.
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2013-1591?
The severity of CVE-2013-1591 is currently unspecified, but it is classified as a stack-based buffer overflow vulnerability.
How do I fix CVE-2013-1591?
To fix CVE-2013-1591, upgrade to the latest version of Pale Moon or affected Red Hat products as noted in the security advisories.
What products are affected by CVE-2013-1591?
CVE-2013-1591 affects several versions of Pale Moon and specific versions of Red Hat Enterprise Virtualization and Enterprise Linux.
What attack vectors are associated with CVE-2013-1591?
CVE-2013-1591 has unspecified impact and context-dependent attack vectors primarily related to the buffer overflow in libpixman.
Can CVE-2013-1591 lead to remote code execution?
While the specifics are not detailed, stack-based buffer overflow vulnerabilities can potentially lead to remote code execution if exploited.