Red Hat Bugzilla – Bug 1462702
CVE-2017-7525 jackson-databind: Deserialization vulnerability via readValue method of ObjectMapper
Last modified: 2018-10-19 17:41:19 EDT
A deserialization flaw in jackson-databind was found allowing code execution when given maliocusly crafted input to readValue method of ObjectMapper.
Acknowledgments: Name: Liao Xinxi (NSFOCUS)
Created jackson-databind tracking bugs for this issue: Affects: fedora-all [bug 1473260]
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform Via RHSA-2017:1836 https://access.redhat.com/errata/RHSA-2017:1836
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 Via RHSA-2017:1835 https://access.redhat.com/errata/RHSA-2017:1835
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 Via RHSA-2017:1834 https://access.redhat.com/errata/RHSA-2017:1834
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 Via RHSA-2017:1837 https://access.redhat.com/errata/RHSA-2017:1837
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS Via RHSA-2017:1839 https://access.redhat.com/errata/RHSA-2017:1839
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 6 Red Hat Software Collections for Red Hat Enterprise Linux 6.7 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS Via RHSA-2017:1840 https://access.redhat.com/errata/RHSA-2017:1840
This issue has been addressed in the following products: Red Hat JBoss Data Virtualization Via RHSA-2017:2477 https://access.redhat.com/errata/RHSA-2017:2477
This issue has been addressed in the following products: Red Hat JBoss BRMS Via RHSA-2017:2547 https://access.redhat.com/errata/RHSA-2017:2547
This issue has been addressed in the following products: Red Hat JBoss BPM Suite Via RHSA-2017:2546 https://access.redhat.com/errata/RHSA-2017:2546
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform Via RHSA-2017:2633 https://access.redhat.com/errata/RHSA-2017:2633
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 7 Via RHSA-2017:2636 https://access.redhat.com/errata/RHSA-2017:2636
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 5 Via RHSA-2017:2637 https://access.redhat.com/errata/RHSA-2017:2637
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Via RHSA-2017:2635 https://access.redhat.com/errata/RHSA-2017:2635
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Via RHSA-2017:2638 https://access.redhat.com/errata/RHSA-2017:2638
Mitigation: Mitigation to this problem is to not trigger polymorphic desrialization globally by using: objectMapper.enableDefaultTyping() and rather use @JsonTypeInfo on the class property to explicitly define the type information. For more information on this issue please refer to https://www.github.com/mbechler/marshalsec/blob/master/marshalsec.pdf?raw=true
Why exactly this task has rhsa_sla flag if it's not Critical?
This issue has been addressed in the following products: RHEV 4.X RHEV-H and Agents for RHEL-7 Via RHSA-2017:3141 https://access.redhat.com/errata/RHSA-2017:3141
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform Via RHSA-2017:3456 https://access.redhat.com/errata/RHSA-2017:3456
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 6 Via RHSA-2017:3454 https://access.redhat.com/errata/RHSA-2017:3454
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 7 Via RHSA-2017:3455 https://access.redhat.com/errata/RHSA-2017:3455
This issue has been addressed in the following products: Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 7 Red Hat JBoss Enterprise Application Platform 7.1 for RHEL 6 Via RHSA-2017:3458 https://access.redhat.com/errata/RHSA-2017:3458
This issue has been addressed in the following products: Red Hat JBoss Data Grid Via RHSA-2018:0294 https://access.redhat.com/errata/RHSA-2018:0294
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.3 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7.4 EUS Via RHSA-2018:0342 https://access.redhat.com/errata/RHSA-2018:0342
Statement: This issue affects the versions of jackson-databind (in Satellite 6.0 and 6.1) and candlepin (which embeds a copy of jackson-databind in Satellite 6.2) as shipped with Red Hat Satellite 6.x. However the affected code is NOT used at this time: Candlepin currently uses the default type resolution configuration for the ObjectMappers it creates/uses. Nowhere in candlepin do we enable global polymorphic deserialization via enableDefaultTyping(...), therefore based on the documentation sited BZ 1462702 , candlepin should not be affected. However as the vulnerable software ships with the product we have marked them as vulnerable to ensure the issue is tracked. JBoss EAP 7.x only uses the vulnerable Jackson Databind library for marshalling and unmarshalling of JSON objects passed to JAX-RS webservices. Some advise about how to remain safe when using JAX-RS webservices on JBoss EAP 7.x is available here: https://access.redhat.com/solutions/3279231 Although JBoss Fuse ships the vulnerable version of jackson-databind, it does not call on enableDefaultTyping() for any polymorphic deserialization operations which is the root cause of this vulnerability. We have raised a Jira tracker to ensure that jackson-databind will be upgraded for Fuse 7.0, however due to feasibility issues jackson-databind cannot be upgraded in JBoss Fuse 6.3.