ghsa-wqv4-9gr3-3qgh
Vulnerability from github
Published
2022-05-14 01:04
Modified
2022-07-01 21:57
Severity ?
Summary
Exposure of Sensitive Information to an Unauthorized Actor in Jenkins
Details
Jenkins 2.73.1 and earlier, 2.83 and earlier provides information about Jenkins user accounts which is generally available to anyone with Overall/Read permissions via the /user/(username)/api remote API. This included e.g. Jenkins users' email addresses if the Mailer Plugin is installed. The remote API now no longer includes information beyond the most basic (user ID and name) unless the user requesting it is a Jenkins administrator.
{ 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-1000395", ], database_specific: { cwe_ids: [ "CWE-200", ], github_reviewed: true, github_reviewed_at: "2022-07-01T21:57:02Z", nvd_published_at: "2018-01-26T02:29:00Z", severity: "MODERATE", }, details: "Jenkins 2.73.1 and earlier, 2.83 and earlier provides information about Jenkins user accounts which is generally available to anyone with Overall/Read permissions via the /user/(username)/api remote API. This included e.g. Jenkins users' email addresses if the Mailer Plugin is installed. The remote API now no longer includes information beyond the most basic (user ID and name) unless the user requesting it is a Jenkins administrator.", id: "GHSA-wqv4-9gr3-3qgh", modified: "2022-07-01T21:57:02Z", published: "2022-05-14T01:04:35Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2017-1000395", }, { type: "WEB", url: "https://github.com/jenkinsci/jenkins/commit/7b1f8e96a8d97dd09e5e093fcdb010b3295acc77", }, { 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:L/I:N/A:N", type: "CVSS_V3", }, ], summary: "Exposure of Sensitive Information to an Unauthorized Actor 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.