Sofy.AI Plugin on Jenkins config.xml cleartext storage
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Sofy.AI Plugin on Jenkins. It has been classified as problematic. Impacted is an unknown function of the file config.xml. This manipulation causes cleartext storage. This vulnerability appears as CVE-2019-10447. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as problematic was found in Sofy.AI Plugin on Jenkins (Artificial Intelligence Software) (unknown version). Affected by this vulnerability is an unknown code block of the file config.xml. The manipulation with an unknown input leads to a cleartext storage vulnerability. The CWE definition for the vulnerability is CWE-312. The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere. As an impact it is known to affect confidentiality. The summary by CVE is:
Jenkins Sofy.AI Plugin stores credentials unencrypted in job config.xml files on the Jenkins master where they can be viewed by users with Extended Read permission, or access to the master file system.
The weakness was presented 10/16/2019 (oss-sec). The advisory is shared at openwall.com. This vulnerability is known as CVE-2019-10447 since 03/29/2019. The exploitation appears to be easy. The attack can be launched remotely. The requirement for exploitation is a single authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1555 for this issue.
By approaching the search of inurl:config.xml it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
See VDB-143522, VDB-143523, VDB-143524 and VDB-143525 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: Cleartext storageCWE: CWE-312 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
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
03/29/2019 🔍10/16/2019 🔍
10/16/2019 🔍
10/16/2019 🔍
Sources
Advisory: openwall.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-10447 (🔍)
GCVE (CVE): GCVE-0-2019-10447
GCVE (VulDB): GCVE-100-143533
See also: 🔍
Entry
Created: 10/16/2019 19:40Updated: 10/16/2019 19:45
Changes: 10/16/2019 19:40 (38), 10/16/2019 19:45 (18)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.