CVE-2025-23215: PMD Designer's release key passphrase (GPG) available on Maven Central in cleartext
Summary While rebuilding PMD Designer for Reproducible Builds and digging into issues, I found out that passphrase for gpg.keyname=0xD0BF1D737C9A1C22 is included in jar published to Maven Central.
Details See https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/net/sourceforge/pmd/pmd-designer/README.md
I removed 2 lines from https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/net/sourceforge/pmd/pmd-designer/pmd-designer-7.0.0.diffoscope but real content is:
├── net/sourceforge/pmd/util/fxdesigner/designer.properties │ @@ -1,14 +1,12 @@ │ #Properties │ checkstyle.plugin.version=3.3.1 │ checkstyle.version=10.14.0 │ -gpg.keyname=0xD0BF1D737C9A1C22 │ -gpg.passphrase=evicx0nuPfvSVhVyeXpw │ jar.plugin.version=3.3.0 │ -java.version=11.0.22 │ +java.version=11.0.25 │ javadoc.plugin.version=3.6.3 │ jflex-output=/home/runner/work/pmd-designer/pmd-designer/target/generated-sources/jflex │ junit5.version=5.8.2 │ kotest.version=5.5.5 │ kotlin.version=1.7.20 │ local.lib.repo=/home/runner/work/pmd-designer/pmd-designer/lib/mvn-repo │ openjfx.scope=provided
PoC ./rebuild.sh content/net/sourceforge/pmd/pmd-designer/pmd-designer-7.0.0.buildspec
Impact After further analysis, the passphrase of the following two keys have been compromised:
1. 94A5 2756 9CAF 7A47 AFCA BDE4 86D3 7ECA 8C2E 4C5B: PMD Designer (Release Signing Key) <releases@pmd-code.org> This key has been used since 2019 with the release of net.sourceforge.pmd:pmd-ui:6.14.0. The following versions are signed with the same key: 6.16.0, 6.17.0, 6.19.0. 2. EBB2 41A5 45CB 17C8 7FAC B2EB D0BF 1D73 7C9A 1C22: PMD Release Signing Key <releases@pmd-code.org> This key has been used since 2020 with the release of net.sourceforge.pmd:pmd-ui:6.21.0 and all the other modules of PMD such as net.sourceforge.pmd:pmd-core:6.21.0. This key has also been used for PMD 7, for the designer, e.g. net.sourceforge.pmd:pmd-designer:7.0.0 and net.sourceforge.pmd:pmd-core:7.0.0. The versions between 6.21.0 and 7.9.0 are signed with this key. Additionally the key has been used to sign the last release of PMD Eclipse Plugin 7.9.0.v20241227-1626-r.
The keys have been used exclusively for signing artifacts that we published to Maven Central under group id net.sourceforge.pmd and once for our pmd-eclipse-plugin. The private key itself is not known to have been compromised itself, but given its passphrase is, it must also be considered potentially compromised.
As a mitigation, both compromised keys have been revoked so that no future use of the keys are possible. For future releases of PMD, PMD Designer and PMD Eclipse Plugin we use a new release signing key: 2EFA 55D0 785C 31F9 56F2 F87E A0B5 CA1A 4E08 6838 (PMD Release Signing Key <releases@pmd-code.org>).
Note, that the published artifacts in Maven Central under the group id net.sourceforge.pmd are not compromised and the signatures are valid. No other past usages of the private key is known to the project and no future use is possible due to the revocation. If anybody finds a past abuse of the private key, please share with us.
Note, the module net.sourceforge.pmd:pmd-ui has been renamed to net.sourceforge.pmd:pmd-designer since PMD 7, so there won't be a fixed version for pmd-ui.
Fixes Reworked build script in PMD Designer to not include all system properties https://github.com/pmd/pmd-designer/commit/1548f5f27ba2981b890827fecbd0612fa70a0362 https://github.com/pmd/pmd-designer/commit/e87a45312753ec46b3e5576c6f6ac1f7de2f5891
References
GHSA-88m4-h43f-wx84 CVE-2025-23215 reproducible-central
Other sources
PMD is an extensible multilanguage static code analyzer. The passphrase for the PMD and PMD Designer release signing keys are included in jar published to Maven Central. The private key itself is not known to have been compromised itself, but given its passphrase is, it must also be considered potentially compromised. As a mitigation, both compromised keys have been revoked so that no future use of the keys are possible. Note, that the published artifacts in Maven Central under the group id net.sourceforge.pmd are not compromised and the signatures are valid.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/net.sourceforge.pmd:pmd-coreto a version that resolves this vulnerability.Fixed in 7.10.0 - Upgrade
Upgrade
maven/net.sourceforge.pmd:pmd-designerto a version that resolves this vulnerability.Fixed in 7.10.0 - Upgrade
Upgrade
PMD Designer (pmd-designer)to a version that resolves this vulnerability.Fixed in 7.0.0 - Configuration
Remove the gpg.keyname/passphrase entries from the build so the PMD release signing key passphrase is no longer embedded in built artifacts (the material shows -gpg.keyname=0xD0BF1D737C9A1C22 and -gpg.passphrase=evicx0nuPfvSVhVyeXpw removed).
PMD Designer build configuration (net/sourceforge/pmd/pmd-designer/pmd-designer-7.0.0.buildspec / designer.properties) gpg.passphrase = evicx0nuPfvSVhVyeXpw (remove) - Configuration
Rework the PMD Designer build script so it does not include all system properties (mitigation referenced in the material for the CVE-2025-23215).
PMD Designer build configuration (net/sourceforge/pmd/pmd-designer/pmd-designer-7.0.0.buildspec / rebuild.sh / buildspec diff) system properties inclusion in PMD Designer build script = not include all system properties - Compensating control
Revoke the two compromised PMD release signing GPG keys so they cannot be used for future artifact signing (keys referenced in the material: gpg.keyname=0xD0BF1D737C9A1C22; and PMD release signing key fingerprint 94A5 2756 9CAF 7A47 AFCA BDE4 86D3 7ECA 8C2E 4C5B).
- Operational
Because the PMD release signing key passphrases were compromised and were included in published JARs, treat the signing key material as potentially compromised and ensure future releases use a new release signing key (as described in the material).
Event History
Frequently Asked Questions
What is the severity of CVE-2025-23215?
CVE-2025-23215 is classified as a moderate severity vulnerability due to the exposure of a passphrase in a publicly accessible JAR file.
How do I fix CVE-2025-23215?
To remediate CVE-2025-23215, upgrade to version 7.10.0 or later of the affected PMD packages.
Which versions of PMD are affected by CVE-2025-23215?
CVE-2025-23215 affects PMD versions from 6.21.0 to 7.0.0 for pmd-core and pmd-designer, and pmd-ui version 6.14.0.
What is the impact of CVE-2025-23215 on PMD users?
The impact of CVE-2025-23215 on PMD users is that sensitive data, specifically a passphrase, may be exposed, potentially compromising security.
Are there any workarounds for CVE-2025-23215?
There are no known workarounds for CVE-2025-23215, and the recommended action is to upgrade to the secure version.