CVE-2011-1525 in the critical feed json
Heap-based buffer overflow in rvrender.dll in RealNetworks RealPlayer 11.0 through 11.1 and 14.0.0 through 14.0.2, and RealPlayer SP 1.0 th…
published 2011-04-06 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1526
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.9%
- EPSS 11.9% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Heap-based buffer overflow in rvrender.dll in RealNetworks RealPlayer 11.0 through 11.1 and 14.0.0 through 14.0.2, and RealPlayer SP 1.0 through 1.1.5, allows remote attackers to execute arbitrary code via a crafted frame in an Internet Video Recording (IVR) file.
Timeline
- First public exploit (EDB-17019)
- Published
Exploit prediction
11.91% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-17019 RealPlayer 14.0.1.633 - Heap Overflow dos, 2011-03-21
- aluigi.org http://aluigi.org/adv/real_5-adv.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/46946 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
-
exploit-db.com
/exploits/17019
exploit
-
aluigi.org
/adv/real_5-adv.txt
exploit
-
securityfocus.com
/bid/46946
vdb-entry, exploit
-
secunia.com
/advisories/43847
third-party-advisory, vendor-advisory
- service.real.com /realplayer/security/04122011_player/en/
-
osvdb.org
/71260
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/66209
vdb-entry
-
securitytracker.com
/id?1025245
vdb-entry
-
securityfocus.com
/archive/1/517083/100/0/threaded
mailing-list
-
securityreason.com
/securityalert/8181
third-party-advisory
Sources
- CVE List CVE-2011-1525
- NVD CVE-2011-1525
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.