Bump com.mchange:c3p0 from 0.11.2 to 0.12.0

[dependabot]

Bumps com.mchange:c3p0 from 0.11.2 to 0.12.0.

Changelog

Sourced from com.mchange:c3p0's changelog.

c3p0-0.12.0 -- Replace com.mchange.v2.naming.permitNonlocalJndiNames with more configurable com.mchange.v2.naming.nameGuardClassName. By default, it is null, and the same "apparently local" restriction previously enforced by com.mchange.v2.naming.permitNonlocalJndiNames is enforced. But users can supply custom com.mchange.v2.naming.NameGuard instances to control what names are permissible, and four implementations of NameGuard are provided. (See the main docs.) -- Documentation updates. -- Disable by default reflective instantiation of javax.naming.spi.ObjectFactory instances unless their classname is included on a whitelist. Define properties-style config parameter com.mchange.v2.naming.objectFactoryWhitelist where the comma-separated whitelist can be provided. By default this parameter contains the two ObjectFactory classes c3p0 includes in references it creates. -- Change the format of userOverridesAsString, which is just a String representation of Map<String,Map<String,String>>. Use a CSV-inspired format, and the mchange-commons-java fastcsv utility, rather than dangerous Java Object serialization of the Map of Maps. -- Disable by default support for resolving references serialized with their own InitialContext custom environment. Define properties-style config parameter com.mchange.v2.naming.acceptDeserializedInitialContextEnvironment, defaulting to false, to manage this dangerous functionality. -- Disable by default JNDI lookups of nonlocal names (conservatively, names that do not seem to be local). For now only String names beginning with "java:" or Name objects whose first component starts with "java:" are considered to be local. Define properties-style config parameter com.mchange.v2.naming.permitNonlocalJndiNames, defaulting to false, to manage this dangerous functionality. -- Disable by default support for loading of javax.naming.spi.ObjectFactory from remote locations via Reference.factoryClassLocation. Define properties-style config parameter com.mchange.v2.naming.supportReferenceRemoteFactoryClassLocation, defaulting to false, to manage this dangerous functionality. -- Fix rare issue in Statement caching (GooGooStatementCache), make sure any Statement we remove is checked into the cache in order to ensure we don't see internal inconsistencies when Statements we mean to cull fail to be removed by removeStatement(...) because they are checked out. Thanks to vimalesh on GitHub for calling attention to this issue. c3p0-0.11.2 -- Expose utilities overwriteJavaBeanProperties and overwriteC3P0PrefixedProperties in the DataSources class, and refactor existing functions to use those. c3p0-0.11.1 -- in BasicResourcePool, forceKillAcquires() accidentally failed to surrender its lock, leading to deadlocks following a full round of acquisition failures. Many thanks to @​pwielgolaski on github for tracking down the issue, to @​driseley on github for providing a reproduction of the issue, and to @​michalgutkowski on github for providing a pull request with the fix. c3p0-0.11.0 -- Additional testing. c3p0-0.11.0-pre2 -- Define new property cancelAutomaticallyClosedStatements, which, if true, ensures that Statement.cancel() will be called prior to Statement.close() when c3p0 automatically close()es statements because a client has neglected to, a Connection with open Statements has exceeded its unreturnedConnectionTimeout, or the Statement cache is expiring a PreparedStatement. Thanks to Andreas Dangel (in 2014!) for pointing out scenarios where this might be

... (truncated)

Commits

• afbb946 Bump version for c3p0-0.12.0 final.
• c5f2445 Documentation updates, RELEASE_NOTES-0.12.0, cap CHANGELOG for c3p0-0.12.0.
• d0d1c50 Modify MarshallUnmarshallDataSourcesJUnitTestCase to include C3P0 config when...
• a42833d Update mchange-commons-java version to 0.4.0.
• 415662b Claude-generated tests of deserialization-gadget mitigations.
• 69dab9c CHANGELOG and documentation updates.
• 5cb3247 Track changes to com.mchange.ser.naming, more flexible control of whether nam...
• 9bef1f6 Update CHANGELOG and docs to more accurately reflect the necessarily imperfec...
• c6f5d11 Centralize some of the jndiName-remoteness testing code, gate mbean- and jbos...
• 155be12 Small documentation fixes.
• Additional commits viewable in compare view

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 commands and options

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 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.

[Surfrdan]

I checked the changelings and this was a simple security patch which the author thinks should not be a breaking change. as all tests pass, I think this can be merged

c3p0-0.12.0, along with its dependency mchange-commons-java-0.4.0, includes mitigations that lock down the functionality misused as gadget chains.

Although it remains possible to resurrect and make use of the dangerous functionality, it requires new, affirmative configuration, and very few contemporary applications should do so.

Most installations will not, but if you experience breaking changes in c3p0-0.12.0, you may need to customize security configuration for your deployment. Please see Configuring Security below for information on how, and for more background on the security issues.