-
Notifications
You must be signed in to change notification settings - Fork 338
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
41 additions
and
0 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
RELEASE NOTES, c3p0-0.9.5.2 | ||
=========================== | ||
|
||
+ This minor bugfix release fixed a bug that caused useless allocation of below-logging-threshold | ||
Strings, and added better debugging information on failed attempts to acquire database Connections. | ||
|
||
|
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
RELEASE NOTES, c3p0-0.9.5.3 | ||
=========================== | ||
|
||
+ This minor bugfix release addresses a security issue: | ||
|
||
CVE-2018-20433, https://nvd.nist.gov/vuln/detail/CVE-2018-20433 | ||
|
||
The c3p0 parsed XML config files liberally, including resolving external | ||
entity references. Incautious use of this feature could permit injection | ||
of malicious config. Now c3p0 does not resolve external entity references | ||
in its the XML config file. | ||
|
||
HOWEVER, in the EXCEEDINGLY RARE CASE that your configuration depends on | ||
the old behavior, if you have UNDERSTOOD the security concern, you may | ||
restore external entity resolution with the following config parameter | ||
(in c3p0.properties, as HOCON config, or as a System property): | ||
|
||
com.mchange.v2.c3p0.cfg.xml.expandEntityReferences=true | ||
|
||
Thanks to user zhutougg on GitHub for calling attention to and suggesting | ||
a fix for this issue. | ||
|
||
+ c3p0 now supports logging to log4j2. (Logging to the old, original log4j | ||
library remains supported as well.) Thanks to user fireandfuel on GitHub | ||
for implementing this feature! (In the mchange-commons-java library.) |