Skip to content
Fencer Intel
critical 9.3

CVE-2009-4588 in the critical feed json

Heap-based buffer overflow in the WindsPlayerIE.View.1 ActiveX control in WindsPly.ocx 3.5.0.0 Beta, 3.0.0.5, and earlier in AwingSoft Awak…

published 16y ago modified 4mo ago also EUVD-2009-4554

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
32.0%
EPSS 32.0% chance of exploitation in 30 days, percentile 98%
public exploits
3
Metasploit and Exploit-DB

Summary

Heap-based buffer overflow in the WindsPlayerIE.View.1 ActiveX control in WindsPly.ocx 3.5.0.0 Beta, 3.0.0.5, and earlier in AwingSoft Awakening Web3D Player and Winds3D Viewer allows remote attackers to cause a denial of service (application crash) or execute arbitrary code via a long SceneUrl property value, a different vulnerability than CVE-2009-2386. NOTE: some of these details are obtained from third party information.

Is CVE-2009-4588 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/browser/awingsoft_web3d_bof)
  2. Published

Exploit prediction

32.04% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/windows/browser/awingsoft_web3d_bof AwingSoft Winds3D Player SceneURL Buffer Overflow metasploit exploit, average rank, 2009-07-10
  • EDB-16524 AwingSoft Winds3D Player - SceneURL Buffer Overflow (Metasploit) remote, 2010-04-30
  • EDB-9116 AwingSoft Web3D Player - 'WindsPly.ocx' Remote Buffer Overflow (PoC) dos, 2009-07-10
  • shinnai.net http://www.shinnai.net/exploits/nsGUdeley3EHfKEV690p.txt referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

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

References

Sources

Fencer Intel 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.