ghsa-876j-4q73-7f56
Vulnerability from github
Published
2022-05-14 03:23
Modified
2022-12-12 21:08
Severity ?
Summary
Jenkins GitHub Pull Request Builder Plugin
Details
GitHub Pull Request Builder Plugin stored the webhook secret shared between Jenkins and GitHub in plain text. This allowed users with Jenkins controller local file system access and Jenkins administrators to retrieve the stored password. The latter could result in exposure of the passwords through browser extensions, cross-site scripting vulnerabilities, and similar situations. GitHub Pull Request Builder Plugin 1.32.1 and newer stores the webhook secret encrypted on disk.
{ affected: [ { package: { ecosystem: "Maven", name: "org.jenkins-ci.plugins:ghprb", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "1.32.1", }, ], type: "ECOSYSTEM", }, ], }, ], aliases: [ "CVE-2018-1000143", ], database_specific: { cwe_ids: [ "CWE-200", ], github_reviewed: true, github_reviewed_at: "2022-12-12T21:08:02Z", nvd_published_at: "2018-04-05T13:29:00Z", severity: "LOW", }, details: "GitHub Pull Request Builder Plugin stored the webhook secret shared between Jenkins and GitHub in plain text. This allowed users with Jenkins controller local file system access and Jenkins administrators to retrieve the stored password. The latter could result in exposure of the passwords through browser extensions, cross-site scripting vulnerabilities, and similar situations. GitHub Pull Request Builder Plugin 1.32.1 and newer stores the webhook secret encrypted on disk.", id: "GHSA-876j-4q73-7f56", modified: "2022-12-12T21:08:02Z", published: "2022-05-14T03:23:44Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2018-1000143", }, { type: "WEB", url: "https://jenkins.io/security/advisory/2018-03-26/#SECURITY-262", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N", type: "CVSS_V3", }, ], summary: "Jenkins GitHub Pull Request Builder Plugin ", }
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.