OctopusDeploy Plugin up to 1.8.1 on Jenkins OctopusDeployPlugin.java server-side request forgery
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in OctopusDeploy Plugin up to 1.8.1 on Jenkins. It has been declared as critical. This vulnerability affects unknown code of the file OctopusDeployPlugin.java. The manipulation leads to server-side request forgery. This vulnerability was named CVE-2019-1003027. The attack can be initiated remotely. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability was found in OctopusDeploy Plugin up to 1.8.1 on Jenkins (Jenkins Plugin). It has been classified as critical. This affects an unknown functionality of the file OctopusDeployPlugin.java. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A server-side request forgery vulnerability exists in Jenkins OctopusDeploy Plugin 1.8.1 and earlier in OctopusDeployPlugin.java that allows attackers with Overall/Read permission to have Jenkins connect to an attacker-specified URL and obtain the HTTP response code if successful, and exception error message otherwise.
The bug was discovered 02/19/2019. The weakness was published 02/20/2019 (Website). It is possible to read the advisory at jenkins.io. This vulnerability is uniquely identified as CVE-2019-1003027 since 02/20/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. The successful exploitation needs a authentication. Technical details of the vulnerability are known, but there is no available exploit.
The vulnerability was handled as a non-public zero-day exploit for at least 1 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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.3
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: Server-side request forgeryCWE: CWE-918
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: 🔍
Timeline
02/19/2019 🔍02/20/2019 🔍
02/20/2019 🔍
02/21/2019 🔍
07/11/2023 🔍
Sources
Advisory: jenkins.ioStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-1003027 (🔍)
GCVE (CVE): GCVE-0-2019-1003027
GCVE (VulDB): GCVE-100-131055
SecurityFocus: 107295
Entry
Created: 02/21/2019 08:06Updated: 07/11/2023 15:40
Changes: 02/21/2019 08:06 (56), 05/11/2020 17:04 (2), 07/11/2023 15:40 (3)
Complete: 🔍
Cache ID: 216:884:103
No comments yet. Languages: en.
Please log in to comment.