ElectricFlow Plugin up to 1.1.5 on Jenkins Permission Check information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in ElectricFlow Plugin up to 1.1.5 on Jenkins and classified as critical. Affected is an unknown function of the component Permission Check. Performing a manipulation results in information disclosure. This vulnerability is reported as CVE-2019-10333. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical has been found in ElectricFlow Plugin up to 1.1.5 on Jenkins (Jenkins Plugin). This affects an unknown part of the component Permission Check. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Missing permission checks in Jenkins ElectricFlow Plugin 1.1.5 and earlier in various HTTP endpoints allowed users with Overall/Read access to obtain information about the Jenkins ElectricFlow Plugin configuration and configuration of connected ElectricFlow instances.
The weakness was disclosed 06/11/2019 (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2019-10333 since 03/29/2019. The exploitability is told to be easy. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-136375, VDB-136376, VDB-136378 and VDB-136379 are pretty similar. 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: 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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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
03/29/2019 🔍06/11/2019 🔍
06/12/2019 🔍
10/03/2023 🔍
Sources
Advisory: openwall.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-10333 (🔍)
GCVE (CVE): GCVE-0-2019-10333
GCVE (VulDB): GCVE-100-136377
SecurityFocus: 108747
See also: 🔍
Entry
Created: 06/12/2019 11:08Updated: 10/03/2023 15:47
Changes: 06/12/2019 11:08 (56), 06/22/2020 17:10 (1), 10/03/2023 15:47 (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.