Skip to content

pf4j vulnerable to remote code execution via loadpluginPath parameter

High severity GitHub Reviewed Published Aug 29, 2023 to the GitHub Advisory Database • Updated Nov 8, 2023

Package

maven org.pf4j:pf4j (Maven)

Affected versions

<= 3.9.0

Patched versions

None

Description

An issue in pf4j pf4j v.3.9.0 and before allows a remote attacker to obtain sensitive information and execute arbitrary code via the loadpluginPath parameter.

References

Published by the National Vulnerability Database Aug 28, 2023
Published to the GitHub Advisory Database Aug 29, 2023
Reviewed Aug 29, 2023
Last updated Nov 8, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.290%
(70th percentile)

Weaknesses

CVE ID

CVE-2023-40827

GHSA ID

GHSA-rvm8-j2cp-j592

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.