{"answers":{"affected":"4 open source packages ship an affected version, including io.github.ascopes:protobuf-maven-plugin.","exploited":"There is no known exploitation of GHSA-j2pc-v64r-mv4f in the wild and no public exploit code.","fix":"Upgrade io.github.ascopes:protobuf-maven-plugin to a fixed version for your release line: 3.10.2 or 4.0.2.","what":"GHSA-j2pc-v64r-mv4f is a vulnerability in io.github.ascopes:protobuf-maven-plugin, published on 4 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-j2pc-v64r-mv4f and fix it if it is affected.\n\nWhat it is: GHSA-j2pc-v64r-mv4f is a vulnerability in io.github.ascopes:protobuf-maven-plugin, published on 4 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-j2pc-v64r-mv4f in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.github.ascopes:protobuf-maven-plugin (Maven): affected all versions; fixed in 3.10.2\n- io.github.ascopes:protobuf-maven-plugin (Maven): affected all versions; fixed in 3.10.2\n- io.github.ascopes:protobuf-maven-plugin (Maven): affected from 4.0.0; fixed in 4.0.2\n- io.github.ascopes:protobuf-maven-plugin (Maven): affected from 4.0.0; fixed in 4.0.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-j2pc-v64r-mv4f/ (Markdown: https://insights.sbomify.com/GHSA-j2pc-v64r-mv4f/index.md)","id":"GHSA-j2pc-v64r-mv4f","markdown":"https://insights.sbomify.com/GHSA-j2pc-v64r-mv4f/index.md","name":"GHSA-j2pc-v64r-mv4f","record":{"aliases":[],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Maven plugin","requires_auth":"none","summary":"The Protobuf Maven Plugin ignores protocDigest when using protoc from PATH, allowing execution of untrusted binaries despite integrity checks.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nThe expected `protocDigest` is ignored when protoc is taken from the `PATH`.\n\n### Details\nThe documentation for the `protocDigest` parameter says:\n\u003e ... Users may wish to specify this if using a `PATH`-based binary ...\n\nHowever, when specifying `\u003cprotoc\u003ePATH\u003c/protoc\u003e` the `protocDigest` is not actually checked because the code returns here already\nhttps://github.com/ascopes/protobuf-maven-plugin/blob/59097aae8062c461129a13dcda2f4116b90a8765/protobuf-maven-plugin/src/main/java/io/github/ascopes/protobufmavenplugin/protoc/ProtocResolver.java#L91-L93\n\nbefore the digest check:\nhttps://github.com/ascopes/protobuf-maven-plugin/blob/59097aae8062c461129a13dcda2f4116b90a8765/protobuf-maven-plugin/src/main/java/io/github/ascopes/protobufmavenplugin/protoc/ProtocResolver.java#L106\n\n### PoC\nSpecify:\n```xml\n\u003cprotoc\u003ePATH\u003c/protoc\u003e\n\u003cprotocDigest\u003esha256:0000000000000000000000000000000000000000000000000000000000000000\u003c/protocDigest\u003e\n```\n\nAnd notice how the `protoc` on the `PATH` is not rejected, despite a digest mismatch.\n\n### Impact\nUsers who have an untrusted `protoc` executable on their `PATH` and rely `\u003cprotocDigest\u003e` as protection are affected.","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Protobuf Maven Plugin protocDigest is ignored when using protoc from PATH","id":"GHSA-j2pc-v64r-mv4f","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["3.10.2"],"introduced":["0"],"last_affected":[],"package":"io.github.ascopes:protobuf-maven-plugin","purl":null,"source":"GHSA-j2pc-v64r-mv4f"},{"ecosystem":"Maven","fixed":["3.10.2"],"introduced":["0"],"last_affected":[],"package":"io.github.ascopes:protobuf-maven-plugin","purl":"pkg:maven/io.github.ascopes/protobuf-maven-plugin","source":"GHSA-j2pc-v64r-mv4f"},{"ecosystem":"Maven","fixed":["4.0.2"],"introduced":["4.0.0"],"last_affected":[],"package":"io.github.ascopes:protobuf-maven-plugin","purl":null,"source":"GHSA-j2pc-v64r-mv4f"},{"ecosystem":"Maven","fixed":["4.0.2"],"introduced":["4.0.0"],"last_affected":[],"package":"io.github.ascopes:protobuf-maven-plugin","purl":"pkg:maven/io.github.ascopes/protobuf-maven-plugin","source":"GHSA-j2pc-v64r-mv4f"}],"products":null,"published":"2025-11-04","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"The Protobuf Maven Plugin ignores protocDigest when using protoc from PATH, allowing execution of untrusted binaries despite integrity checks.","url":"https://insights.sbomify.com/GHSA-j2pc-v64r-mv4f/"}