Fix to Google Issue 212 #2
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
to know if an uncaught exception is a security exception or usual runtime exception.
|
extending to EnterpriseRuntimeSecurityException creates an error, will look up to that. |
ghost
closed this
ghost
reopened this
This was referenced Nov 13, 2014
Closed
|
Did you discover why extending EnterpriseRuntimeSecurityException errors? This should be an unchecked / runtime exception. |
xeno6696
added a commit
that referenced
this pull request
Jan 20, 2016
Pull new history for experimentation.
xeno6696
added a commit
that referenced
this pull request
May 13, 2018
Moved esapi.tld into the correct resources location. Fixes issues #2…
ghost
mentioned this pull request
xeno6696
pushed a commit
to xeno6696/esapi-java-legacy
that referenced
this pull request
Jun 27, 2025
kwwall
added a commit
that referenced
this pull request
Jun 27, 2025
* Fix javadoc botch forgetting to end italics. :( * Added new static method 'isMethodExplicityEnabled' abd other minor Javadoc tweaks. * Added default exception message if one wasn't specified or was empty. * Changed to use a more politically correct property name. But I still like 'ESAPI.enableLegCannonModeAndGetMyAssFired.justification' better. ;-) * Add code to ensure that DefaultEncoder.encodeForSQL is explicity enabled if someone wants to use it. * Updating ESAPI util for ExplictMethod verify Updating parameter null check to test null case. Removing null check on property result (if null ConfigurationException is thrown). Simplifying return from method to verify response is not empty. * ESAPI methodEnabled Tests Adding branch testing for ESAPI.isMethodExplicitlyEnabled behavior to account for parameter cases. Only case not covered is providing an ESAPI.properties that does not contain the new key. * Test Coverage using the SecurityConfigurationWrapper to verify remaining test case when a ConfigurationException is thrown when the new property is missing or undefined. * Added deprecations, deprecation warnings, and other Javadoc refinements. * Reference specific CVE ID for logged message. * Change from EVENT_FAILURE to SECURITY_FAILURE, because it potentially is, despite best intentions. * Draft #2. Needs reviewd and completed. Track changes disabled. * Apparently {@inheritdoc} doesn't inherit @deprecated from interfaces. Plus minor type fix ('class' ==> 'method'). * Draft 3 - completed several more sections. * Minor corrections to ESAPI Security Bulletin #13. * Update to FileUploads 1.6.0 to address CVE-2025-48976, which likely didn't affect HTTPUtilities.getFileUploads interaces anyway. * Implement java.util.function.Supplier since we are using Java 8 for a while. * Incorporate Jeremiah Stacey's feedback. * Incorporate Erika von Kampen's feedback. * Final draft of Security Bulletin #13 until CVE published. (Need to include its summary description.) * Fix minor typos. * Update versions of spotbugs-maven-plugin and maven-pmd-plugin. * Update previous release date. * release info for 2.7.0.0 * ESAPI 2.7.0.0 release notes. --------- Co-authored-by: kwwall <[email protected]> Co-authored-by: jeremiah.stacey <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
to know if an uncaught exception is a security exception or usual runtime exception.