RHSA-2018:0342: Important: rh-maven35-jackson-databind security update

Published Feb 22, 2018
·
Updated

The jackson-databind package provides general data-binding functionality for Jackson, which works on top of Jackson core streaming API.Security Fix(es): A deserialization flaw was discovered in the jackson-databind which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. (CVE-2017-7525) Further classes that an attacker could use to achieve code execution through deserialisation were discovered, and added to the blacklist introduced by CVE-2017-7525. (CVE-2017-15095, CVE-2017-17485) Red Hat would like to thank Liao Xinxi (NSFOCUS) for reporting CVE-2017-7525 and CVE-2017-15095 and 0c0c0f from 360观星实验室 for reporting CVE-2017-17485.

Affected Software

3 affected componentsFixes available
redhat/rh-maven35-jackson-databind<2.7.6-2.4.el7
2.7.6-2.4.el7
redhat/rh-maven35-jackson-databind<2.7.6-2.4.el7
2.7.6-2.4.el7
redhat/rh-maven35-jackson-databind-javadoc<2.7.6-2.4.el7
2.7.6-2.4.el7

Remediation

Event History

Mar 28, 2026
Advisory Published
via Red Hat·08:55 AM
Data Sourced
via Red Hat·08:55 AM
RemedyDescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of RHSA-2018:0342?

The severity of RHSA-2018:0342 is critical due to a deserialization flaw in jackson-databind that can allow unauthorized code execution.

2

How can I fix RHSA-2018:0342?

To fix RHSA-2018:0342, upgrade jackson-databind to version 2.7.6-2.4.el7 or later.

3

Which software is affected by RHSA-2018:0342?

RHSA-2018:0342 affects the rh-maven35-jackson-databind package in versions prior to 2.7.6-2.4.el7.

4

Is RHSA-2018:0342 vulnerable to remote attacks?

Yes, RHSA-2018:0342 is vulnerable to remote attacks, as it allows unauthenticated users to exploit the deserialization flaw.

5

What are the consequences of not addressing RHSA-2018:0342?

Failure to address RHSA-2018:0342 may result in unauthorized access and execution of arbitrary code on the affected systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203