Your message dated Wed, 15 Jul 2020 01:15:18 +0200
with message-id <[email protected]>
and subject line jackson-databind: consider using a whitelist
has caused the Debian Bug report #941662,
regarding jackson-databind: consider using a whitelist
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
941662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941662
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: jackson-databind
Version: 2.10.0-1
Severity: grave
Tags: security upstream
Justification: user security hole
Forwarded: https://github.com/FasterXML/jackson-databind/issues/2478
Control: found -1 2.9.8-3
Control: found -1 2.8.6-1+deb9u5
Control: found -1 2.8.6-1
Hi,
Tony, Markus, As it was already expected ;-). Upstream, whilst it
affects as well 2.10.0, seemigly is not considering doing an update
for 2.10 specifically but have fixed this one as well for older
versions. Previous point, that this is just going to start to be silly
upholds.
That said, let's follow with the usual information:
The following vulnerabilities were published for jackson-databind.
CVE-2019-16942[0]:
| A Polymorphic Typing issue was discovered in FasterXML jackson-
| databind 2.0.0 through 2.9.10. When Default Typing is enabled (either
| globally or for a specific property) for an externally exposed JSON
| endpoint and the service has the commons-dbcp (1.4) jar in the
| classpath, and an attacker can find an RMI service endpoint to access,
| it is possible to make the service execute a malicious payload. This
| issue exists because of
| org.apache.commons.dbcp.datasources.SharedPoolDataSource and
| org.apache.commons.dbcp.datasources.PerUserPoolDataSource mishandling.
CVE-2019-16943[1]:
| A Polymorphic Typing issue was discovered in FasterXML jackson-
| databind 2.0.0 through 2.9.10. When Default Typing is enabled (either
| globally or for a specific property) for an externally exposed JSON
| endpoint and the service has the p6spy (3.8.6) jar in the classpath,
| and an attacker can find an RMI service endpoint to access, it is
| possible to make the service execute a malicious payload. This issue
| exists because of com.p6spy.engine.spy.P6DataSource mishandling.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2019-16942
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16942
[1] https://security-tracker.debian.org/tracker/CVE-2019-16943
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16943
[2] https://github.com/FasterXML/jackson-databind/issues/2478
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Upstream enabled Safe Default Typing by default which is a mitigation
against the "polymorphic de-serialization" CVE we have seen in the past.
I don't think a whitelist is necessary anymore, the upstream feature
should be used instead. The unsafe variant enableDefaultTyping is
deprecated and will be removed in 3.0. New similar CVE should be treated
as minor and no-dsa, an occasional point update should be fine though.
https://medium.com/@cowtowncoder/jackson-2-10-safe-default-typing-2d018f0ce2ba
Markus
signature.asc
Description: OpenPGP digital signature
--- End Message ---
__
This is the maintainer address of Debian's Java team
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
[email protected] for discussions and questions.
