Skip to content

OPSC-17995 Upgrade commons-compress 1.10 -> 1.27.1 to fix CVEs, bump version to 2.7.0.13 - #18

Open
orion104 wants to merge 62 commits into
masterfrom
OPSC-17995-equifax-security-concerns
Open

OPSC-17995 Upgrade commons-compress 1.10 -> 1.27.1 to fix CVEs, bump version to 2.7.0.13#18
orion104 wants to merge 62 commits into
masterfrom
OPSC-17995-equifax-security-concerns

Conversation

@orion104

@orion104 orion104 commented Aug 2, 2026

Copy link
Copy Markdown
Collaborator

What is the issue

Customer (Equifax) reported 5 CVEs in OpsCenter caused by the commons-compress 1.10 jar bundled inside jython-standalone, tracked in OPSC-17995.

Because commons-compress is embedded inside the jython-standalone fat jar, it cannot be excluded via Gradle. The fix requires rebuilding jython-standalone with an updated commons-compress version and publishing a new artifact.

What does this PR fix and why was it fixed

  • Upgraded commons-compress from 1.101.27.1 (resolves all 5 reported CVEs, well past the required minimum of 1.21)
  • Bumped the jython-standalone artifact version from 2.7.0.122.7.0.13
  • Fixed Ant build to generate ANTLR sources with JDK 8 compatibility and committed pre-generated sources to avoid runtime NPE

The new 2.7.0.13 artifact is consumed by riptano/ripcord in the companion PR for OPSC-17995.

Tom Alexander and others added 30 commits February 11, 2016 11:42
Account for IPV6 in hostname stuff
Don't cause deadlocks closing sockets.
This reverts commit beeb2f7, reversing
changes made to 693694d.
Fixes two somewhat related issues with respect to closing sockets:

* Peer closes do not mean the socket is no longer writable, just that
  the peer has closed its half of the channel (half-closed). Fixed by
  always allowing the channel to be written to once half closed (#2470).

* Server sockets now shutdown their thread pools asynchronously with
  their closing, so as to not deadlock (#2471).
…pletes #2471

Although adding the corresponding listener can produces noisy tests
(in test_socket) due to finalization racing with thread pool shutdown,
it also ensures these thread pools are in fact cleaned up.

See netty/netty#2166 - perhaps we can
control logging to remove this noise in stderr.
Add ability to deploy to artifactory
…nce. Fixes #2469

Jython accommodates jar shading by attempting to import packages first
from shaded namespaces (via Jar Jar Links); then the usual
namespace. In general, we prefer our bundled packages to prevent
versioning issues, however for BC this does not work, because Java
security providers (or at least BC as the relevant example) require
signed jars, which breaks the shading model.

Given that BC is especially stable in its API, this should (hopefully)
not present an issue for Jython.
This reverts commit 3d2cbb4.
nickmbailey and others added 30 commits August 4, 2016 17:11
…y cert in the pem file. Workarounds issue #2516
12032 - Improve TLS errors during handshakes
Fix options so they actually work, set hard defaults
* Add explicit namespace to org.python.jnr imports
* Version bump
NoVerifyX509TrustManager was removed by the SNI commit (f6ee772)
but ripcord 6.8.x SslUtils.py still imports it. Reverting until
SNI support is properly integrated as part of OPSC-16690.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants