Repository navigation
Conversation
…false positive The fix for CVE-2016-4000 (readResolve() in PyFunction blocking deserialization) has been present in ripcord-master since the branch was forked from upstream (commit 4c33721). However, vulnerability scanners flag any version < 2.7.4 by version string alone. Bump version 2.7.0.16 -> 2.7.0.17 so the published jar reflects that this fix is intentionally included in this DataStax fork build. Ref: https://datastax.jira.com/browse/OPSC-18029 CVE: https://nvd.nist.gov/vuln/detail/CVE-2016-4000
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Bumps the version string from
2.7.0.16→2.7.0.17inbuild.xml.Background
CVE-2016-4000 (CVSS 9.8 Critical) is a Java deserialization vulnerability in Jython via
PyFunctionobjects. The actual fix has been present inripcord-mastersince the branch was forked from upstream — commit4c337213b("Do not deserialize PyFunction objects. Fixes #2454") is commit jython#67 in the branch history, andjavapon the publishedjython-standalone-2.7.0.16.jarconfirmsprivate java.lang.Object readResolve();exists inorg.python.core.PyFunction.However, customers and their vulnerability scanners flag OpsCenter 6.8.53/6.8.54 because they compare the version string against the NVD entry (
< 2.7.4= vulnerable). Since2.7.0.16<2.7.4numerically, the scanner triggers even though the code is patched.Fix
Pure version bump — no code changes. Republishing as
2.7.0.17documents that this build intentionally includes the deserialization fix, and will at minimum resolve scanners using DataStax-internal version tracking.Changes
build.xml:jython.versionandjython.version.noplus2.7.0.16→2.7.0.17References