CVE-2015-4681 json
Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allows local users to have unspecified impact via vectors related to weak passw…
published 9y ago modified 4mo ago also EUVD-2015-4700
- cvss
- 7.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 1
- Exploit-DB
Summary
Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allows local users to have unspecified impact via vectors related to weak passwords.
Is CVE-2015-4681 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 (EDB-37449)
- Published
Exploit prediction
1.70% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-37449 Polycom RealPresence Resource Manager < 8.4 - Multiple Vulnerabilities webapps, 2015-06-30
- seclists.org http://seclists.org/fulldisclosure/2015/Jun/81 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-255 Credentials Management Errors
References
-
exploit-db.com
/exploits/37449/
exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2015/Jun/81
mailing-list, exploit, third-party-advisory, vdb-entry
-
support.polycom.com
/global/documents/support/documentation/Security_Center_Post_for_RPRM_CVEs.pdf
vendor-advisory
-
packetstormsecurity.com
/files/132463/Polycom-RealPresence-Resource-Manager-RPRM-Disclosure-Traversal.html
third-party-advisory, vdb-entry
-
securityfocus.com
/archive/1/535852/100/0/threaded
mailing-list
-
securityfocus.com
/bid/75432
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2015-4681
- NVD CVE-2015-4681
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.