openid Plugin on Jenkins OpenIdSsoSecurityRealm.DescriptorImpl#doValidate cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in openid Plugin on Jenkins. This affects the function OpenIdSsoSecurityRealm.DescriptorImpl#doValidate. The manipulation leads to cross-site request forgery.
This vulnerability is referenced as CVE-2019-1003098. Remote exploitation of the attack is possible. No exploit is available.
Details
A vulnerability was found in openid Plugin on Jenkins (Jenkins Plugin) (the affected version is unknown) and classified as problematic. This issue affects the function OpenIdSsoSecurityRealm.DescriptorImpl#doValidate. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to 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. Impacted is integrity. The summary by CVE is:
A cross-site request forgery vulnerability in Jenkins openid Plugin in the OpenIdSsoSecurityRealm.DescriptorImpl#doValidate form validation method allows attackers to initiate a connection to an attacker-specified server.
The bug was discovered 04/03/2019. The weakness was published 04/04/2019 (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2019-1003098 since 04/03/2019. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. 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 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.
Similar entries are available at VDB-132978, VDB-132979, VDB-132980 and VDB-132981. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
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: 🔍
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
04/03/2019 🔍04/03/2019 🔍
04/04/2019 🔍
04/05/2019 🔍
08/25/2023 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
Confirmation: 🔍
CVE: CVE-2019-1003098 (🔍)
GCVE (CVE): GCVE-0-2019-1003098
GCVE (VulDB): GCVE-100-133025
SecurityFocus: 107790
See also: 🔍
Entry
Created: 04/05/2019 08:53Updated: 08/25/2023 14:44
Changes: 04/05/2019 08:53 (55), 06/23/2020 11:00 (3), 08/25/2023 14:44 (3)
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.