How severe is GHSA-hrwc-pqfm-g6qf?

GHSA-hrwc-pqfm-g6qf has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-hrwc-pqfm-g6qf?

GHSA-hrwc-pqfm-g6qf affects the following packages: org.jenkins-ci.plugins:subversion (Maven). Ecosystems affected: Maven.

How do I fix GHSA-hrwc-pqfm-g6qf?

Update org.jenkins-ci.plugins:subversion to 2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrwc-pqfm-g6qf is resolved across your whole dependency graph.

How do I detect GHSA-hrwc-pqfm-g6qf in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:subversion, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hrwc-pqfm-g6qf if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-hrwc-pqfm-g6qf actively exploited in the wild?

No public exploit code has been indexed for GHSA-hrwc-pqfm-g6qf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hrwc-pqfm-g6qf?

GHSA-hrwc-pqfm-g6qf has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hrwc-pqfm-g6qf?

GHSA-hrwc-pqfm-g6qf is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hrwc-pqfm-g6qf published, and has it been updated?

GHSA-hrwc-pqfm-g6qf was published on May 17, 2022 and was last updated on February 21, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

Jenkins Subversion Plugin Cross-Site Request Forgery vulnerabilityGHSA-hrwc-pqfm-g6qf

MEDIUM

GHSA-hrwc-pqfm-g6qf is a medium-severity (CVSS 6.5) Cross-Site Request Forgery (CSRF) vulnerability in org.jenkins-ci.plugins:subversion. A fix is available for org.jenkins-ci.plugins:subversion — see the affected versions and patch details below.

Also known asCVE-2017-1000085

Published

May 17, 2022

Updated

Feb 21, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕org.jenkins-ci.plugins:subversion

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Subversion Plugin connects to a user-specified Subversion repository as part of form validation (e.g. to retrieve a list of tags). This functionality improperly checked permissions, allowing any user with Item/Build permission (but not Item/Configure) to connect to any web server or Subversion server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery attacks. As of version 2.9, this functionality properly checks permissions and is only available via POST.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:subversion`	all versions	2.9`org.jenkins-ci.plugins:subversion:2.9`

Affected Products

1 product · 1 configurations

Application

subversionjenkins

≤ 2.8

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:subversion, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:subversion to 2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hrwc-pqfm-g6qf is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

This issue affects the versions of jenkins-plugin-subversion as shipped with Red Hat OpenShift Enterprise 3. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification:…

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 3.6	`atomic-openshift-0:3.6.173.0.21-1.git.0.f95b0e7.el7`	RHBA-2017:2642

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-hrwc-pqfm-g6qf in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

May 17, 2022

Last updated

Feb 21, 2024

Identifiers

GHSA-hrwc-pqfm-g6qf

References

Advisorynvd.nist.gov · CVE 2017 1000085 Webjenkins.io · 2017 07 10 Webweb.archive.org Packagegithub.com · subversion plugin

Related vulnerabilities

This CVE is medium severity, in line with the other 8 CVEs affecting subversion.

CVE-2021-21698CVE-2020-2304CVE-2020-2111CVE-2013-6372CVE-2017-1000085CVE-2018-1000111CVE-2022-29048CVE-2022-29046

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedFeb 21, 2024

Jenkins Subversion Plugin Cross-Site Request Forgery vulnerabilityGHSA-hrwc-pqfm-g6qf

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Fixing This On Your OS

Frequently Asked Questions

Is GHSA-hrwc-pqfm-g6qf in your dependencies?