CVE-2010-0214 json
The administrative interface on the PolyVision RoomWizard with firmware 3.2.3 places the Sync Connector Active Directory (AD) credentials i…
published 15y ago modified 4mo ago also EUVD-2010-0245
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.9%
- EPSS 1.9% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
The administrative interface on the PolyVision RoomWizard with firmware 3.2.3 places the Sync Connector Active Directory (AD) credentials in a web form that is accessed over HTTP on port 80, which allows remote attackers to obtain sensitive information by reading the HTML source code corresponding to the /admin/sign/DeviceSynch URI.
Is CVE-2010-0214 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 FencerExploit prediction
1.92% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.org http://packetstormsecurity.org/files/view/97291/roomwizard-disclose.txt referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2011/Jan/58 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
packetstormsecurity.org
/files/view/97291/roomwizard-disclose.txt
exploit
-
seclists.org
/fulldisclosure/2011/Jan/58
mailing-list, exploit
-
vupen.com
/english/advisories/2011/0059
vdb-entry, vendor-advisory
-
kb.cert.org
/vuls/id/870601
third-party-advisory, us-government-resource
-
exchange.xforce.ibmcloud.com
/vulnerabilities/64543
vdb-entry
-
securityfocus.com
/bid/45699
vdb-entry
Sources
- CVE List CVE-2010-0214
- NVD CVE-2010-0214
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.