Ricoh Aficio MP 301 Wizard adrsSetUserWizard.cgi entryNameIn Stored cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Ricoh Aficio MP 301. This affects an unknown part of the file /web/entry/en/address/adrsSetUserWizard.cgi of the component Wizard. The manipulation of the argument entryNameIn as part of Parameter results in cross site scripting (Stored). This vulnerability is known as CVE-2018-17312. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability, which was classified as problematic, was found in Ricoh Aficio MP 301 (unknown version). Affected is an unknown code block of the file /web/entry/en/address/adrsSetUserWizard.cgi of the component Wizard. The manipulation of the argument entryNameIn as part of a Parameter leads to a cross site scripting vulnerability (Stored). CWE is classifying the issue as CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. This is going to have an impact on integrity. CVE summarizes:
On the RICOH Aficio MP 301 printer, HTML Injection and Stored XSS vulnerabilities have been discovered in the area of adding addresses via the entryNameIn parameter to /web/entry/en/address/adrsSetUserWizard.cgi.
The bug was discovered 09/24/2018. The weakness was published 09/26/2018 (Website). The advisory is shared for download at packetstormsecurity.com. This vulnerability is traded as CVE-2018-17312 since 09/21/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.1
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: StoredClass: Cross site scripting / Stored
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/21/2018 🔍09/24/2018 🔍
09/26/2018 🔍
09/26/2018 🔍
09/27/2018 🔍
05/19/2023 🔍
Sources
Advisory: 149496Status: Not defined
CVE: CVE-2018-17312 (🔍)
GCVE (CVE): GCVE-0-2018-17312
GCVE (VulDB): GCVE-100-124500
Entry
Created: 09/27/2018 09:12Updated: 05/19/2023 09:09
Changes: 09/27/2018 09:12 (59), 03/27/2020 10:12 (1), 05/19/2023 09:09 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.