Jpom
Monthly
Jpom through 2.11.12 exposes a broken object-level authorization flaw on the /build/branch-list endpoint, letting any authenticated user supply a repositoryId belonging to a different workspace and have the server resolve it without verifying ownership. This enables cross-workspace repository enumeration, disclosure of repository type, and execution of git ls-remote calls that reuse another workspace's stored Git credentials, leaking private repository metadata. Exploitation is low-complexity over the network with only a low-privileged account required, and publicly available exploit code exists, though the CVSS 4.0 base score is only 5.3 because the impact is limited to confidentiality.
Jpom through 2.11.12 exposes a broken object-level authorization flaw on the /build/branch-list endpoint, letting any authenticated user supply a repositoryId belonging to a different workspace and have the server resolve it without verifying ownership. This enables cross-workspace repository enumeration, disclosure of repository type, and execution of git ls-remote calls that reuse another workspace's stored Git credentials, leaking private repository metadata. Exploitation is low-complexity over the network with only a low-privileged account required, and publicly available exploit code exists, though the CVSS 4.0 base score is only 5.3 because the impact is limited to confidentiality.