Publisher Over CIFS Plugin up to 0.10 on Jenkins CIFS Server CifsPublisherPluginDescriptor.java confused deputy
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Publisher Over CIFS Plugin up to 0.10 on Jenkins. The affected element is an unknown function of the file CifsPublisherPluginDescriptor.java of the component CIFS Server. The manipulation leads to confused deputy. This vulnerability is listed as CVE-2018-1999038. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Publisher Over CIFS Plugin up to 0.10 on Jenkins (Jenkins Plugin) and classified as critical. This issue affects some unknown processing of the file CifsPublisherPluginDescriptor.java of the component CIFS Server. The manipulation with an unknown input leads to a confused deputy vulnerability. Using CWE to declare the problem leads to CWE-441. The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
A confused deputy vulnerability exists in Jenkins Publisher Over CIFS Plugin 0.10 and earlier in CifsPublisherPluginDescriptor.java that allows attackers to have Jenkins connect to an attacker specified CIFS server with attacker specified credentials.
The bug was discovered 07/30/2018. The weakness was presented 08/01/2018 (Website). The advisory is shared at jenkins.io. The identification of this vulnerability is CVE-2018-1999038 since 08/01/2018. The attack may be initiated remotely. Required for exploitation is a simple authentication. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
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
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.0
VulDB Temp Score: 5.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.2
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: Confused deputyCWE: CWE-441
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: 🔍
Timeline
07/30/2018 🔍08/01/2018 🔍
08/01/2018 🔍
08/01/2018 🔍
08/02/2018 🔍
03/12/2020 🔍
Sources
Advisory: jenkins.ioStatus: Not defined
Confirmation: 🔍
CVE: CVE-2018-1999038 (🔍)
GCVE (CVE): GCVE-0-2018-1999038
GCVE (VulDB): GCVE-100-122513
Entry
Created: 08/02/2018 07:57Updated: 03/12/2020 16:08
Changes: 08/02/2018 07:57 (58), 03/12/2020 16:08 (2)
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.