Skip to content
Fencer Vulns
low 2.1

CVE-2008-1943 json

Buffer overflow in the backend of XenSource Xen Para Virtualized Frame Buffer (PVFB) 3.0 through 3.1.2 allows local users to cause a denial…

published 2008-05-14 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1942

cvss
2.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

Buffer overflow in the backend of XenSource Xen Para Virtualized Frame Buffer (PVFB) 3.0 through 3.1.2 allows local users to cause a denial of service (crash) and possibly execute arbitrary code via a crafted description of a shared framebuffer.

Patch / fix

  • xen RHEL 5 VIRTUALIZATION, RHEL 5 3.0.3-41.el5_1.5
  • xen-libs RHEL 5 3.0.3-41.el5_1.5

red hat advisories RHSA-2008:0194

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2008-1943 updated

PVFB backend fails to validate frontend's framebuffer description

  • Red Hat Enterprise Linux (v. 5 server) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5 Red Hat Enterprise Linux Desktop (v. 5 client) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5 Red Hat Enterprise Linux Desktop Multi OS (v. 5 client) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5 Red Hat Enterprise Linux Virtualization (v. 5 server) xen 3.0.3-41.el5_1.5, xen-libs 3.0.3-41.el5_1.5
    fixed: vendor fix RHSA-2008:0194

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 2.1 AV:L/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.