Skip to content
Fencer Intel
critical 9.3

CVE-2010-0688 in the critical feed json

Stack-based buffer overflow in Orbital Viewer 1.04 allows user-assisted remote attackers to execute arbitrary code via a crafted (1) .orb o…

published 16y ago modified 4mo ago also EUVD-2010-0715

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

Summary

Stack-based buffer overflow in Orbital Viewer 1.04 allows user-assisted remote attackers to execute arbitrary code via a crafted (1) .orb or (2) .ov file.

Is CVE-2010-0688 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 (EDB-11581)
  2. Published

Exploit prediction

37.78% 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/fileformat/orbital_viewer_orb Orbital Viewer ORB File Parsing Buffer Overflow metasploit exploit, great rank, 2010-02-27
  • EDB-16654 Orbital Viewer - '.ORB' File Parsing Buffer Overflow (Metasploit) local, 2010-03-09
  • EDB-13940 Orbital Viewer 1.04 - '.ov' Local Universal Stack Overflow (SEH) local, 2010-06-19
  • EDB-11581 Orbital Viewer 1.04 - '.orb' File Local Universal Overflow (SEH) local, 2010-02-26
  • corelan.be http://www.corelan.be:8800/index.php/forum/security-advisories/corelan-10-011-orbital-viewer-orb-buffer-overflow/ referenced PoC, tagged "exploit" by a source, unverified
  • securityfocus.com http://www.securityfocus.com/bid/38436 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.