typora up to 0.9.81/0.9.9.31.2 on macOS/Linux File cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in typora up to 0.9.81/0.9.9.31.2 on macOS/Linux. Affected is an unknown function of the component File Handler. Performing a manipulation results in cross site scripting. This vulnerability is identified as CVE-2019-20374. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, was found in typora up to 0.9.81/0.9.9.31.2 on macOS/Linux. This affects some unknown functionality of the component File Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability. CWE is classifying the issue as CWE-80. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as "<", ">", and "&" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages. This is going to have an impact on integrity. The summary by CVE is:
A mutation cross-site scripting (XSS) issue in Typora through 0.9.9.31.2 on macOS and through 0.9.81 on Linux leads to Remote Code Execution through Mermaid code blocks. To exploit this vulnerability, one must open a file in Typora. The XSS vulnerability is then triggered due to improper HTML sanitization. Given that the application is based on the Electron framework, the XSS leads to remote code execution in an unsandboxed environment.
The weakness was released 01/09/2020. This vulnerability is uniquely identified as CVE-2019-20374 since 01/09/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
- 0.9.0
- 0.9.1
- 0.9.2
- 0.9.3
- 0.9.4
- 0.9.5
- 0.9.6
- 0.9.7
- 0.9.8
- 0.9.9
- 0.9.9.31.0
- 0.9.9.31.1
- 0.9.9.31.2
- 0.9.10
- 0.9.11
- 0.9.12
- 0.9.13
- 0.9.14
- 0.9.15
- 0.9.16
- 0.9.17
- 0.9.18
- 0.9.19
- 0.9.20
- 0.9.21
- 0.9.22
- 0.9.23
- 0.9.24
- 0.9.25
- 0.9.26
- 0.9.27
- 0.9.28
- 0.9.29
- 0.9.30
- 0.9.31
- 0.9.32
- 0.9.33
- 0.9.34
- 0.9.35
- 0.9.36
- 0.9.37
- 0.9.38
- 0.9.39
- 0.9.40
- 0.9.41
- 0.9.42
- 0.9.43
- 0.9.44
- 0.9.45
- 0.9.46
- 0.9.47
- 0.9.48
- 0.9.49
- 0.9.50
- 0.9.51
- 0.9.52
- 0.9.53
- 0.9.54
- 0.9.55
- 0.9.56
- 0.9.57
- 0.9.58
- 0.9.59
- 0.9.60
- 0.9.61
- 0.9.62
- 0.9.63
- 0.9.64
- 0.9.65
- 0.9.66
- 0.9.67
- 0.9.68
- 0.9.69
- 0.9.70
- 0.9.71
- 0.9.72
- 0.9.73
- 0.9.74
- 0.9.75
- 0.9.76
- 0.9.77
- 0.9.78
- 0.9.79
- 0.9.80
- 0.9.81
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.1VulDB Meta Temp Score: 7.1
VulDB Base Score: 4.7
VulDB Temp Score: 4.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.3
NVD Vector: 🔍
CNA Base Score: 8.3
CNA Vector (MITRE): 🔍
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-80 / CWE-74 / CWE-707
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: 🔍
Patch: github.com
Timeline
01/09/2020 🔍01/09/2020 🔍
01/10/2020 🔍
03/20/2024 🔍
Sources
Advisory: 4e8af7b2c4a159b683d317e02c5cbddb86dc4a0eStatus: Not defined
CVE: CVE-2019-20374 (🔍)
GCVE (CVE): GCVE-0-2019-20374
GCVE (VulDB): GCVE-100-148521
Entry
Created: 01/10/2020 08:12Updated: 03/20/2024 14:10
Changes: 01/10/2020 08:12 (35), 01/10/2020 08:17 (11), 03/20/2024 14:09 (18), 03/20/2024 14:10 (19)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.