Luigi up to 2.7.x API Endpoint spotify/luigi/pull/1870 id cross-site request forgery
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.4 | $0-$5k | 0.00 |
A vulnerability has been found in Luigi up to 2.7.x and classified as problematic. Affected by this vulnerability is an unknown part of the file spotify/luigi/pull/1870 of the component API Endpoint. The manipulation of the argument id
as part of a Parameter 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:
Luigi version prior to version 2.8.0; after commit 53b52e12745075a8acc016d33945d9d6a7a6aaeb; after GitHub PR spotify/luigi/pull/1870 contains a Cross ite Request Forgery (CSRF) vulnerability in API endpoint: /api/<method> that can result in Task metadata such as task name, id, parameter, etc. will be leaked to unauthorized users. This attack appear to be exploitable via The victim must visit a specially crafted webpage from the network where their Luigi server is accessible.. This vulnerability appears to have been fixed in 2.8.0 and later.
The bug was discovered 10/01/2016. The weakness was presented 12/20/2018 (Website). The advisory is shared at github.com. This vulnerability is known as CVE-2018-1000843 since 12/20/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 810 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.8.0 eliminates this vulnerability. Applying the patch 53b52e12745075a8acc016d33945d9d6a7a6aaeb is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.
See VDB-277172, VDB-277174, VDB-277175 and VDB-278140 for similar entries.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔍VulDB CVSS-BT Score: 🔍
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
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
Class: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Luigi 2.8.0
Patch: 53b52e12745075a8acc016d33945d9d6a7a6aaeb
Timeline
10/01/2016 🔍12/20/2018 🔍
12/20/2018 🔍
12/20/2018 🔍
12/21/2018 🔍
06/20/2023 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2018-1000843 (🔍)
See also: 🔍
Entry
Created: 12/21/2018 10:40 AMUpdated: 06/20/2023 09:16 AM
Changes: 12/21/2018 10:40 AM (61), 04/22/2020 12:56 PM (1), 06/20/2023 09:16 AM (4)
Complete: 🔍
Cache ID: 35:966:40
No comments yet. Languages: en.
Please log in to comment.