dependabot[bot] opened a new pull request, #223: URL: https://github.com/apache/servicemix-bundles/pull/223
Bumps [org.owasp.esapi:esapi](https://github.com/ESAPI/esapi-java-legacy) from 2.5.1.0 to 2.5.2.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ESAPI/esapi-java-legacy/releases";>org.owasp.esapi:esapi's releases</a>.</em></p> <blockquote> <h2>2.5.2.0</h2> <h3>Release Notes</h3> <p>The release notes for ESAPI release 2.5.2.0 are located at: <a href="https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/esapi4java-core-2.5.2.0-release-notes.txt";>https://github.com/ESAPI/esapi-java-legacy/blob/develop/documentation/esapi4java-core-2.5.2.0-release-notes.txt</a></p> <h3>Configuration files located in configuration jar</h3> <p>Note that the attached file "<strong>esapi-2.5.2.0-configuration.jar</strong>" contains the default ESAPI configuration files intended for used in production. Download the file and unjar it via 'jar xf'. After you unjar that configuration jar, look under the 'configuration/' directory. Most of the files you are interested in are located under 'configuration/esapi', such as ESAPI.properties, validation.properties, etc. The attached file "esapi-2.5.2.0-configuration.jar.asc" is a detached GPG signature of that the file "esapi-2.5.2.0-configuration.jar" that was signed by ESAPI project co-lead, Kevin W. Wall.</p> <h3>CVEs addressed</h3> <ul> <li>CVE-2023-24998 was remediated. See Security Bulletin 11 for details.</li> <li><a href="https://nvd.nist.gov/vuln/detail/CVE-2023-26119";>CVE-2023-26119</a> was remediated. It is not yet know if it impacted ESAPI.</li> </ul> <p>The release notes contain a more complete list of what has changed / fixed in ESAPI 2.5.2.0.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/15737a23c0eb171da45148583d388edb023ff4b3";><code>15737a2</code></a> Minor updates to release steps to mention problems that maven-site-plugin and...</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/ded3c13d7fb11cefdc107f35382be5e3ef477df2";><code>ded3c13</code></a> Update commits based on final release prep.</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/fc4f466ebc19b3e7942627f0faccc8fb346a02b9";><code>fc4f466</code></a> Correct release date to 4/12/2023.</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/74a57300075af8e1e37a17f2e4d0fa042490ffe5";><code>74a5730</code></a> Remove '-SNAPSHOT' suffix for official release.</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/fea010ae4c9c1d00299c73b3bb51657a66376c64";><code>fea010a</code></a> Initial 2.5.2.0 release preparation (<a href="https://redirect.github.com/ESAPI/esapi-java-legacy/issues/784";>#784</a>)</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/3230ed92c32a87e4ac73bfc38ad0a4128edcd51e";><code>3230ed9</code></a> Update table of releases in SECURITY.md</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/33ba9d87b5ff9e76ca8b72e91a268cf48b59e02a";><code>33ba9d8</code></a> How CVE-2023-24998 impacts ESAPI -- major rewrite</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/d9f9fc123244281230b9ef4a7519230678244f5c";><code>d9f9fc1</code></a> CVE-2023-24998 and Security Bulletin <a href="https://redirect.github.com/ESAPI/esapi-java-legacy/issues/11";>#11</a></li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/74abc7951ba110a49e0c448480523e79eaf7e9d6";><code>74abc79</code></a> How CVE-2023-24998 impacts ESAPI</li> <li><a href="https://github.com/ESAPI/esapi-java-legacy/commit/5ef77388d548eb3191ab81bab8f77abd5fe6e7a3";><code>5ef7738</code></a> Upgrade the maven site and related plugins, and other little cleanup. (<a href="https://redirect.github.com/ESAPI/esapi-java-legacy/issues/779";>#779</a>)</li> <li>Additional commits viewable in <a href="https://github.com/ESAPI/esapi-java-legacy/compare/esapi-2.5.1.0...esapi-2.5.2.0";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/servicemix-bundles/network/alerts). </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
