Firefly III 4.7.17.5 Liability Name Field Stored cross site scripting
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
4.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Firefly III 4.7.17.5. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Liability Name Field Handler. The manipulation leads to cross site scripting (Stored). This vulnerability is handled as CVE-2019-14672. The attack may be launched remotely. There is no exploit available. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Details
A vulnerability was found in Firefly III 4.7.17.5. It has been declared as problematic. Affected by this vulnerability is an unknown functionality of the component Liability Name Field Handler. The manipulation with an unknown input leads to a cross site scripting vulnerability (Stored). The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
Firefly III 4.7.17.5 is vulnerable to stored XSS due to the lack of filtration of user-supplied data in the liability name field. The JavaScript code is executed upon an error condition during a visit to the account show page.
The weakness was published 08/05/2019. This vulnerability is known as CVE-2019-14672 since 08/05/2019. The attack can be launched remotely. The successful exploitation needs a single authentication. 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.
Similar entries are available at VDB-139524, VDB-139523, VDB-139522 and VDB-139521. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.4VulDB Meta Temp Score: 4.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
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: 🔍
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
08/05/2019 🔍08/05/2019 🔍
08/06/2019 🔍
11/20/2023 🔍
Sources
Advisory: 8717f469b10e9f7e1547c6f70f7d24e1359d28d4Status: Not defined
CVE: CVE-2019-14672 (🔍)
GCVE (CVE): GCVE-0-2019-14672
GCVE (VulDB): GCVE-100-139525
See also: 🔍
Entry
Created: 08/06/2019 07:38 AMUpdated: 11/20/2023 05:25 PM
Changes: 08/06/2019 07:38 AM (36), 07/21/2020 11:13 AM (17), 11/20/2023 05:25 PM (5)
Complete: 🔍
Cache ID: 18:F85:40
No comments yet. Languages: en.
Please log in to comment.