Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2017-1000084

Incorrect Default Permissions

Published: Oct 05, 2017 | Modified: Oct 03, 2019
CVSS 3.x
6.5
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
CVSS 2.x
4 MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2017-1000084
CWEhttps://cwe.mitre.org/data/definitions/276.html

Parameterized Trigger Plugin fails to check Item/Build permission: The Parameterized Trigger Plugin did not check the build authentication it was running as and allowed triggering any other project in Jenkins.

Weakness

During installation, installed file permissions are set to allow anyone to modify those files.

Affected Software

Name Vendor Start Version End Version
Parameterized_trigger Jenkins 1.0 (including) 1.0 (including)
Parameterized_trigger Jenkins 1.1 (including) 1.1 (including)
Parameterized_trigger Jenkins 1.2 (including) 1.2 (including)
Parameterized_trigger Jenkins 1.3 (including) 1.3 (including)
Parameterized_trigger Jenkins 1.4 (including) 1.4 (including)
Parameterized_trigger Jenkins 1.5 (including) 1.5 (including)
Parameterized_trigger Jenkins 1.6 (including) 1.6 (including)
Parameterized_trigger Jenkins 2.0 (including) 2.0 (including)
Parameterized_trigger Jenkins 2.1 (including) 2.1 (including)
Parameterized_trigger Jenkins 2.2 (including) 2.2 (including)
Parameterized_trigger Jenkins 2.3 (including) 2.3 (including)
Parameterized_trigger Jenkins 2.4 (including) 2.4 (including)
Parameterized_trigger Jenkins 2.5 (including) 2.5 (including)
Parameterized_trigger Jenkins 2.6 (including) 2.6 (including)
Parameterized_trigger Jenkins 2.7 (including) 2.7 (including)
Parameterized_trigger Jenkins 2.8 (including) 2.8 (including)
Parameterized_trigger Jenkins 2.9 (including) 2.9 (including)
Parameterized_trigger Jenkins 2.10 (including) 2.10 (including)
Parameterized_trigger Jenkins 2.11 (including) 2.11 (including)
Parameterized_trigger Jenkins 2.12 (including) 2.12 (including)
Parameterized_trigger Jenkins 2.13 (including) 2.13 (including)
Parameterized_trigger Jenkins 2.14 (including) 2.14 (including)
Parameterized_trigger Jenkins 2.15 (including) 2.15 (including)
Parameterized_trigger Jenkins 2.16 (including) 2.16 (including)
Parameterized_trigger Jenkins 2.17 (including) 2.17 (including)
Parameterized_trigger Jenkins 2.18 (including) 2.18 (including)
Parameterized_trigger Jenkins 2.19 (including) 2.19 (including)
Parameterized_trigger Jenkins 2.20 (including) 2.20 (including)
Parameterized_trigger Jenkins 2.21 (including) 2.21 (including)
Parameterized_trigger Jenkins 2.22 (including) 2.22 (including)
Parameterized_trigger Jenkins 2.23 (including) 2.23 (including)
Parameterized_trigger Jenkins 2.24 (including) 2.24 (including)
Parameterized_trigger Jenkins 2.25 (including) 2.25 (including)
Parameterized_trigger Jenkins 2.26 (including) 2.26 (including)
Parameterized_trigger Jenkins 2.27 (including) 2.27 (including)
Parameterized_trigger Jenkins 2.28 (including) 2.28 (including)
Parameterized_trigger Jenkins 2.29 (including) 2.29 (including)
Parameterized_trigger Jenkins 2.30 (including) 2.30 (including)
Parameterized_trigger Jenkins 2.31 (including) 2.31 (including)
Parameterized_trigger Jenkins 2.32 (including) 2.32 (including)
Parameterized_trigger Jenkins 2.33 (including) 2.33 (including)
Parameterized_trigger Jenkins 2.34 (including) 2.34 (including)

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2024 Aqua Security Software Ltd.   Privacy Policy | Terms of Use