| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in YAFNET up to 3.1.11. This issue affects some unknown processing of the component Signature Handler. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2023-0650. The attack is possible to be carried out remotely. Moreover, an exploit is present. It is recommended to upgrade the affected component.
Details
A vulnerability was found in YAFNET up to 3.1.11 and classified as problematic. This issue affects some unknown processing of the component Signature Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity.
The weakness was disclosed 02/02/2023 by Chun-Li Lin with CHT Security Co., Ltd.. The advisory is shared at drive.google.com. The identification of this vulnerability is CVE-2023-0650. It demands that the victim is doing some kind of user interaction. Technical details are unknown but a public exploit is available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
The exploit is available at drive.google.com. It is declared as proof-of-concept.
Upgrading to version 3.1.12 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch a1442a2bacc3335461b44c250e81f8d99c60735f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
Website
- Product: https://github.com/YAFNET/YAFNET/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.1VulDB Meta Temp Score: 4.0
VulDB Base Score: 3.5
VulDB Temp Score: 3.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CNA Base Score: 3.5
CNA Vector (VulDB): 🔍
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
Class: Cross site scriptingCWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: YAFNET 3.1.12
Patch: a1442a2bacc3335461b44c250e81f8d99c60735f
Timeline
02/02/2023 🔍02/02/2023 🔍
02/02/2023 🔍
03/01/2023 🔍
Sources
Product: github.comAdvisory: a1442a2bacc3335461b44c250e81f8d99c60735f
Researcher: Chun-Li Lin
Organization: CHT Security Co., Ltd.
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2023-0650 (🔍)
GCVE (CVE): GCVE-0-2023-0650
GCVE (VulDB): GCVE-100-220037
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/02/2023 14:43Updated: 03/01/2023 20:17
Changes: 02/02/2023 14:43 (44), 02/02/2023 14:51 (5), 02/13/2023 09:58 (8), 02/13/2023 10:01 (3), 03/01/2023 20:09 (3), 03/01/2023 20:17 (19)
Complete: 🔍
Submitter: lin7lic
Committer: lin7lic
Cache ID: 216::103
Submit
Accepted
- Submit #79467: YAFNET XSS in EditSignature Page (by lin7lic)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.