You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
c3p0:c3p0 is a lIbrary for augmenting traditional (DriverManager-based) JDBC drivers with JNDI-bindable DataSources, including DataSources that implement Connection and Statement Pooling, as described by the jdbc3 spec and jdbc2 std extension. Note: This library is no longer maintained and has migrated to the artifact
"com.mchange:c3p0"
Affected versions of this package are vulnerable to XML External Entity (XXE) Injection.
via the extractXmlConfigFromInputStream in com/mchange/v2/c3p0/cfg/C3P0ConfigXmlUtils.java during initialization.
Details
XXE Injection is a type of attack against an application that parses XML input.
XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.
Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.
For example, below is a sample XML document, containing an XML element- username.
An external XML entity - xxe, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of /etc/passwd and display it to the user rendered by username.
Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.
Package Name: c3p0:c3p0
Package Version: ['0.9.1.2']
Package Manager: maven
Target File: todolist-core/pom.xml
Severity Level: critical
Snyk ID: SNYK-JAVA-C3P0-461017
Snyk CVE: CVE-2018-20433
Snyk CWE: CWE-611
Link to issue in Snyk: https://app.snyk.io/org/rhicksiii91/project/deb9d3bf-7122-4824-acbf-cd302b957776
Snyk Description: ## Overview
c3p0:c3p0 is a lIbrary for augmenting traditional (DriverManager-based) JDBC drivers with JNDI-bindable DataSources, including DataSources that implement Connection and Statement Pooling, as described by the jdbc3 spec and jdbc2 std extension. Note: This library is no longer maintained and has migrated to the artifact
"com.mchange:c3p0"
Affected versions of this package are vulnerable to XML External Entity (XXE) Injection.
via the
extractXmlConfigFromInputStream
incom/mchange/v2/c3p0/cfg/C3P0ConfigXmlUtils.java
during initialization.Details
XXE Injection is a type of attack against an application that parses XML input.
XML is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. By default, many XML processors allow specification of an external entity, a URI that is dereferenced and evaluated during XML processing. When an XML document is being parsed, the parser can make a request and include the content at the specified URI inside of the XML document.
Attacks can include disclosing local files, which may contain sensitive data such as passwords or private user data, using file: schemes or relative paths in the system identifier.
For example, below is a sample XML document, containing an XML element- username.
An external XML entity -
xxe
, is defined using a system identifier and present within a DOCTYPE header. These entities can access local or remote content. For example the below code contains an external XML entity that would fetch the content of/etc/passwd
and display it to the user rendered byusername
.Other XXE Injection attacks can access local resources that may not stop returning data, possibly impacting application availability and leading to Denial of Service.
Remediation
There is no fixed version for
c3p0:c3p0
.References
The text was updated successfully, but these errors were encountered: