Boteraser | Website and Server Security Solutions
Recommended update for mojo-parent
This update for mojo-parent fixes the following issues:
xalan-j2 was updated from version 2.7.2 to 2.7.3:
mojo-parent was updated from version 70 to 82:
+ mojo.java.target should be set as '8', without '1.'
+ spotless plugin must be executed by JDK 11 at least
+ ossrh-snapshots repository was removed from parent
+ Removed SHA-512 checksum for source release artifact
+ Use only project version as tag for release
+ Added space before close empty elements in poms by spotless
+ Using Checkstyle together with Spotless
+ Introduce spotless for automatic code formatting
+ Introduce enforcer rule for minimal version of Java and Maven
+ Use new Plugin Tools report - maven-plugin-report-plugin
+ Added sisu-maven-plugin
+ Introduced maven.version property
+ Execute spotless by JDK 11 at least
+ Use release options for m-compiler-p with newer JDKs
+ Allow override of invoker.streamLogsOnFailures
+ Require Maven 3.9.x at least for releases
+ Added maven-wrapper-plugin to pluginManagement
+ Removed ossrh-snapshots repository from MojoHaus parent
+ Added build-helper-maven-plugin to pluginManagement
+ Require Maven 3.6.3+
+ Updated palantirJavaFormat for spotless - JDK 21 compatible
+ Added dependencyManagement for maven-shade-plugin
+ Dropped recommendedJavaBuildVersion property
+ Format Markdown files with Spotless Plugin
+ Restore source release distribution in child projects
+ Rename property maven.version to mavenVersion
+ minimalMavenBuildVersion should not be overriding by
mavenVersion
+ Use simple checkstyle rules since spotless is executed by
default
+ Use old spotless version only for JDK < 11
+ Fixed spotless configuration for markdown
bcel was updated from version 5.2 to 6.10:
apache-commons-lang3 was updated to version 3.12.0 to 3.16.0:
xerces-j2:
netty3:
SUSE-RU-2024:3971-1 is recorded against 7 packages.
Published on 11 November 2024 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
Details
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| apache-commons-lang3 | — | 3.16.0-150200.3.9.2 |
| bcel | — | 6.10.0-150200.11.6.2 |
| mojo-parent | — | 82-150200.3.10.1 |
| netty3 | — | 3.10.6-150200.3.13.2 |
| xalan-j2 | — | 2.7.3-150200.11.7.1 |
| xalan-j2-extras | — | 2.7.3-150200.11.7.1 |
| xerces-j2 | — | 2.12.2-150200.3.10.2 |
References
Similar Threats
Free Vulnerability Check
BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against SUSE-RU-2024:3971-1 and other known CVE records.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
Stay up to date with the latest from Boteraser.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Manage your cookie preferences below:
Essential cookies enable basic functions and are necessary for the proper function of the website.
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
Service URL: developers.cloudflare.com (opens in a new window)
These cookies are needed for adding comments on this website.
These cookies are used for managing login functionality on this website.
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Service URL: policies.google.com (opens in a new window)
You can find more information in our Cookie Policy and Privacy Policy.