Togglz up to 2.9.3 Console cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Togglz up to 2.9.3. It has been classified as problematic. Affected by this vulnerability is an unknown functionality of the component Console. This manipulation causes cross-site request forgery. This vulnerability is registered as CVE-2020-28191. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic was found in Togglz up to 2.9.3. Affected by this vulnerability is an unknown code block of the component Console. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:
The console in Togglz before 2.9.4 allows CSRF.
The weakness was published 12/27/2022 as GHSA-697v-pxg3-j262. The advisory is shared at github.com. This vulnerability is known as CVE-2020-28191 since 11/02/2020. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.9.4 eliminates this vulnerability. Applying the patch ed66e3f584de954297ebaf98ea4a235286784707 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
License
Website
- Product: https://github.com/togglz/togglz/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Togglz 2.9.4
Patch: ed66e3f584de954297ebaf98ea4a235286784707
Timeline
11/02/2020 🔍12/27/2022 🔍
12/27/2022 🔍
12/27/2022 🔍
Sources
Product: github.comAdvisory: GHSA-697v-pxg3-j262
Status: Confirmed
CVE: CVE-2020-28191 (🔍)
GCVE (CVE): GCVE-0-2020-28191
GCVE (VulDB): GCVE-100-216865
Entry
Created: 12/27/2022 09:52Changes: 12/27/2022 09:52 (42)
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.