What is GHSA-J2PC-V64R-MV4F?

GHSA-J2PC-V64R-MV4F is a low-severity security vulnerability in io.github.ascopes:protobuf-maven-plugin (maven), affecting versions >= 4.0.0, <= 4.0.1. It is fixed in 4.0.2, 3.10.2.

Which versions of io.github.ascopes:protobuf-maven-plugin are affected by GHSA-J2PC-V64R-MV4F?

io.github.ascopes:protobuf-maven-plugin (maven) versions >= 4.0.0, <= 4.0.1 is affected.

Is there a fix for GHSA-J2PC-V64R-MV4F?

Yes. GHSA-J2PC-V64R-MV4F is fixed in 4.0.2, 3.10.2. Upgrade to this version or later.

Is GHSA-J2PC-V64R-MV4F exploitable, and should I be worried?

Whether GHSA-J2PC-V64R-MV4F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-J2PC-V64R-MV4F is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-J2PC-V64R-MV4F

Q: Which versions of io.github.ascopes:protobuf-maven-plugin are affected by GHSA-J2PC-V64R-MV4F?

io.github.ascopes:protobuf-maven-plugin (maven) versions >= 4.0.0, <= 4.0.1 is affected.

Q: Is there a fix for GHSA-J2PC-V64R-MV4F?

Yes. GHSA-J2PC-V64R-MV4F is fixed in 4.0.2, 3.10.2. Upgrade to this version or later.

Q: Is GHSA-J2PC-V64R-MV4F exploitable, and should I be worried?

Whether GHSA-J2PC-V64R-MV4F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-J2PC-V64R-MV4F is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-J2PC-V64R-MV4F?

Upgrade: io.github.ascopes:protobuf-maven-plugin to 4.0.2 or later, io.github.ascopes:protobuf-maven-plugin to 3.10.2 or later.

Summary

Protobuf Maven Plugin protocDigest is ignored when using protoc from PATH

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.

Affected versions

io.github.ascopes:protobuf-maven-plugin (>= 4.0.0, <= 4.0.1) io.github.ascopes:protobuf-maven-plugin (< 3.10.2)

Security releases

io.github.ascopes:protobuf-maven-plugin → 4.0.2 (maven) io.github.ascopes:protobuf-maven-plugin → 3.10.2 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

io.github.ascopes:protobuf-maven-plugin to 4.0.2 or later; io.github.ascopes:protobuf-maven-plugin to 3.10.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-J2PC-V64R-MV4F? GHSA-J2PC-V64R-MV4F is a low-severity security vulnerability in io.github.ascopes:protobuf-maven-plugin (maven), affecting versions >= 4.0.0, <= 4.0.1. It is fixed in 4.0.2, 3.10.2.
Which versions of io.github.ascopes:protobuf-maven-plugin are affected by GHSA-J2PC-V64R-MV4F? io.github.ascopes:protobuf-maven-plugin (maven) versions >= 4.0.0, <= 4.0.1 is affected.
Is there a fix for GHSA-J2PC-V64R-MV4F? Yes. GHSA-J2PC-V64R-MV4F is fixed in 4.0.2, 3.10.2. Upgrade to this version or later.
Is GHSA-J2PC-V64R-MV4F exploitable, and should I be worried? Whether GHSA-J2PC-V64R-MV4F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-J2PC-V64R-MV4F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-J2PC-V64R-MV4F?
- Upgrade io.github.ascopes:protobuf-maven-plugin to 4.0.2 or later
- Upgrade io.github.ascopes:protobuf-maven-plugin to 3.10.2 or later