CVE-2010-1318 in the critical feed json
Stack-based buffer overflow in the AgentX::receive_agentx function in AgentX++ 1.4.16, as used in RealNetworks Helix Server and Helix Mobil…
published 16y ago modified 4mo ago also EUVD-2010-1347
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 58.1%
- EPSS 58.1% chance of exploitation in 30 days, percentile 99%
- public exploits
- 3
- Metasploit and Exploit-DB
Summary
Stack-based buffer overflow in the AgentX::receive_agentx function in AgentX++ 1.4.16, as used in RealNetworks Helix Server and Helix Mobile Server 11.x through 13.x and other products, allows remote attackers to execute arbitrary code via unspecified vectors.
Is CVE-2010-1318 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 FencerTimeline
- First public exploit (Metasploit exploit/windows/misc/agentxpp_receive_agentx)
- Published
Exploit prediction
58.05% chance of exploitation in the next 30 days, higher than 99% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/misc/agentxpp_receive_agentx AgentX++ Master AgentX::receive_agentx Stack Buffer Overflow metasploit exploit, good rank, 2010-04-16
- EDB-16452 AgentX++ Master - AgentX::receive_agentx Stack Buffer Overflow (Metasploit) remote, 2010-05-11
- EDB-12274 Multiple Vendor AgentX++ - Stack Buffer Overflow (PoC) dos, 2010-04-17
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
secunia.com
/advisories/39279
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2010/0889
vdb-entry, vendor-advisory
-
securityfocus.com
/bid/39490
vdb-entry
- realnetworks.com /uploadedFiles/Support/helix-support/SecurityUpdate041410HS.pdf
Sources
- CVE List CVE-2010-1318
- NVD CVE-2010-1318
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.