CVE-2009-1660: Stack-based buffer overflow in URUWorks ViPlay3 3.0 and earlier allows remote attackers to cause a denial of s

Q: How do I fix CVE-2009-1660?

viplay3: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2009-1660 being exploited?

CVE-2009-1660 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2009-1660 affect?

CVE-2009-1660 affects viplay3. Severity is high (CVSS 9.3). Stack-based buffer overflow in URUWorks ViPlay3 3.0 and earlier allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long file entry in a .vpl file.

Q: How urgent is CVE-2009-1660?

Priority 61/100. Critical severity; EPSS top 7%: very likely to be exploited; Public exploit reference

This week

HIGH 9.3DOWNGRADE

CVE-2009-1660 is a high-severity flaw (CVSS 9.3) affecting viplay3. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Stack-based buffer overflow in URUWorks ViPlay3 3.0 and earlier allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long file entry in a .vpl file.

Why this priority

Critical severity
EPSS top 7%: very likely to be exploited
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.3 (High)
EPSS exploit chance	5.8% (top 7%)
CISA exploited list	No
Weakness	CWE-119
Published	2009-05-18
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: urusoft

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2009-05-18 12:00 UTCPublished CVE record published
2026-06-16 23:07 UTCUpdated Record last modified

urusoft viplay3 DOWNGRADE

Affected: 3.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.0

1. Check installed version

apt-cache policy viplay3 || rpm -q viplay3 || viplay3 --version

2. No fixed release: DOWNGRADE to a release before 3.0 (Debian / Ubuntu)

apt-cache madison viplay3 sudo apt install viplay3=<VERSION_BEFORE_3.0> sudo apt-mark hold viplay3

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list viplay3 sudo dnf downgrade viplay3-<VERSION_BEFORE_3.0> sudo dnf versionlock add viplay3

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

Exploit-DB: ViPlay3 < 3.00 - '.vpl' Local Stack Overflow (PoC)

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2009-1660?

viplay3: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2009-1660 being exploited?

CVE-2009-1660 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2009-1660 affect?

CVE-2009-1660 affects viplay3. Severity is high (CVSS 9.3). Stack-based buffer overflow in URUWorks ViPlay3 3.0 and earlier allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long file entry in a .vpl file.

How urgent is CVE-2009-1660?

Priority 61/100. Critical severity; EPSS top 7%: very likely to be exploited; Public exploit reference

References

← Back to latest CVEs