PT-2025-46976 · Maven · Io.Github.Ascopes:Protobuf-Maven-Plugin

Published 2025-11-04 · Updated 2025-11-04

OSV

CVSS v4.0

1.0

Low

Base vector

AV:L/AC:H/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N

Summary

The expected protocDigest is ignored when protoc is taken from the PATH.

Details

The documentation for the protocDigest parameter says:

... Users may wish to specify this if using a PATH-based binary ...

However, when specifying <protoc>PATH</protoc> the protocDigest is not actually checked because the code returns here already https://github.com/ascopes/protobuf-maven-plugin/blob/59097aae8062c461129a13dcda2f4116b90a8765/protobuf-maven-plugin/src/main/java/io/github/ascopes/protobufmavenplugin/protoc/ProtocResolver.java#L91-L93

before the digest check: https://github.com/ascopes/protobuf-maven-plugin/blob/59097aae8062c461129a13dcda2f4116b90a8765/protobuf-maven-plugin/src/main/java/io/github/ascopes/protobufmavenplugin/protoc/ProtocResolver.java#L106

PoC

Specify:

<protoc>PATH</protoc>
<protocDigest>sha256:0000000000000000000000000000000000000000000000000000000000000000</protocDigest>

And notice how the protoc on the PATH is not rejected, despite a digest mismatch.

Impact

Users who have an untrusted protoc executable on their PATH and rely <protocDigest> as protection are affected.

Fix

Protection Mechanism Failure

Weakness Enumeration

CWE-354

CWE-693

Related Identifiers

GHSA-J2PC-V64R-MV4F

Affected Products

Io.Github.Ascopes:Protobuf-Maven-Plugin

References · 4

• https://osv.dev/vulnerability/GHSA-j2pc-v64r-mv4f · Vendor Advisory
• https://github.com/ascopes/protobuf-maven-plugin/security/advisories/GHSA-j2pc-v64r-mv4f · Note
• https://github.com/ascopes/protobuf-maven-plugin · Note
• https://github.com/ascopes/protobuf-maven-plugin/commit/d3330e7038a296fe595c5470a22019eb70e35b07 · Note