Team Concert Plugin up to 1.3.0 on Jenkins Permission Check Credentials improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Team Concert Plugin up to 1.3.0 on Jenkins and classified as problematic. The impacted element is an unknown function of the component Permission Check. Performing a manipulation results in improper authorization (Credentials). This vulnerability is reported as CVE-2019-16567. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as problematic, was found in Team Concert Plugin up to 1.3.0 on Jenkins (Jenkins Plugin). This affects an unknown part of the component Permission Check. The manipulation with an unknown input leads to a improper authorization vulnerability (Credentials). CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality. The summary by CVE is:
A missing permission check in Jenkins Team Concert Plugin 1.3.0 and earlier in form-related methods allowed users with Overall/Read access to enumerate credentials ID of credentials stored in Jenkins.
The weakness was disclosed 12/17/2019 (oss-sec). The advisory is shared at openwall.com. This vulnerability is uniquely identified as CVE-2019-16567 since 09/20/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 T1548.002 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-147279, VDB-147280, VDB-147281 and VDB-147282 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: 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
Name: CredentialsClass: Improper authorization / Credentials
CWE: CWE-285 / 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
09/20/2019 🔍12/17/2019 🔍
12/18/2019 🔍
12/18/2019 🔍
Sources
Advisory: openwall.comStatus: Not defined
Confirmation: 🔍
CVE: CVE-2019-16567 (🔍)
GCVE (CVE): GCVE-0-2019-16567
GCVE (VulDB): GCVE-100-147297
See also: 🔍
Entry
Created: 12/18/2019 07:38Updated: 12/18/2019 07:43
Changes: 12/18/2019 07:38 (40), 12/18/2019 07:43 (18)
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.