ghsa-j472-mcq2-95p6
Vulnerability from github
Published
2022-05-14 01:04
Modified
2022-07-01 21:58
Severity ?
Summary
OS Command Injection in Jenkins
Details
Jenkins 2.73.1 and earlier, 2.83 and earlier users with permission to create or configure agents in Jenkins could configure a launch method called 'Launch agent via execution of command on master'. This allowed them to run arbitrary shell commands on the master node whenever the agent was supposed to be launched. Configuration of this launch method now requires the Run Scripts permission typically only granted to administrators.
{ affected: [ { database_specific: { last_known_affected_version_range: "<= 2.73.1", }, package: { ecosystem: "Maven", name: "org.jenkins-ci.main:jenkins-core", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "2.73.2", }, ], type: "ECOSYSTEM", }, ], }, { database_specific: { last_known_affected_version_range: "<= 2.83", }, package: { ecosystem: "Maven", name: "org.jenkins-ci.main:jenkins-core", }, ranges: [ { events: [ { introduced: "2.74", }, { fixed: "2.84", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2017-1000393", ], database_specific: { cwe_ids: [ "CWE-78", ], github_reviewed: true, github_reviewed_at: "2022-07-01T21:58:54Z", nvd_published_at: "2018-01-26T02:29:00Z", severity: "HIGH", }, details: "Jenkins 2.73.1 and earlier, 2.83 and earlier users with permission to create or configure agents in Jenkins could configure a launch method called 'Launch agent via execution of command on master'. This allowed them to run arbitrary shell commands on the master node whenever the agent was supposed to be launched. Configuration of this launch method now requires the Run Scripts permission typically only granted to administrators.", id: "GHSA-j472-mcq2-95p6", modified: "2022-07-01T21:58:54Z", published: "2022-05-14T01:04:30Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2017-1000393", }, { type: "WEB", url: "https://github.com/jenkinsci/jenkins/commit/67f68c181033cbabf2075769e0f846f58c226c08", }, { type: "WEB", url: "https://github.com/jenkinsci/jenkins/commit/d7ea3f40efedd50541a57b943d5f7bbed046d091", }, { type: "PACKAGE", url: "https://github.com/jenkinsci/jenkins", }, { type: "WEB", url: "https://jenkins.io/security/advisory/2017-10-11", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", type: "CVSS_V3", }, ], summary: "OS Command Injection in Jenkins", }
Log in or create an account to share your comment.
Security Advisory comment format.
This schema specifies the format of a comment related to a security advisory.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.