CVE-2008-1952: Buffer Overflow

Published May 15, 2008
·
Updated

Description of problem:

The recent fix to validate the frontend's frame buffer description neglected to limit the frame buffer size correctly. This lets a malicious frontend make the backend attempt to map an arbitrary amount of guest memory, which could be useful for a denial of service attack against dom0.

Proposed upstream patch:

http://xenbits.xensource.com/xen-unstable.hg?rev/9044705960cb30cec385bdca7305bcf7db096721

Other sources

The backend for XenSource Xen Para Virtualized Frame Buffer (PVFB) in Xen ioemu does not properly restrict the frame buffer size, which allows attackers to cause a denial of service (crash) by mapping an arbitrary amount of guest memory.

Red Hat

Affected Software

2 affected componentsFixes available
redhat/xen<0:3.0.3-64.el5_2.3
0:3.0.3-64.el5_2.3
xensource Xen Para Virtualized Frame Buffer

Event History

May 15, 2008
CVE Published
via Red Hat·12:00 AM
May 21, 2008
Data Sourced
via Red Hat·04:55 PM
DescriptionSeverityAffected Software
Jun 23, 2008
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2008-1952?

CVE-2008-1952 is classified as a denial of service vulnerability which can lead to a system crash.

2

How do I fix CVE-2008-1952?

To mitigate CVE-2008-1952, update to the version 0:3.0.3-64.el5_2.3 or newer for the affected Xen package.

3

What products are affected by CVE-2008-1952?

CVE-2008-1952 affects the XenSource Xen Para Virtualized Frame Buffer, specifically the older versions of the Xen package.

4

What attacks can be performed using CVE-2008-1952?

An attacker can exploit CVE-2008-1952 to map an arbitrary amount of guest memory, causing a denial of service.

5

Is there a known workaround for CVE-2008-1952?

Currently, the primary recommendation for CVE-2008-1952 is to apply the necessary updates rather than relying on a workaround.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203