– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Gentoo Linux Security Advisory GLSA 201710-28
– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
https://security.gentoo.org/
– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Severity: Normal
Title: Jython: Arbitrary code execution
Date: October 29, 2017
Bugs: #621876
ID: 201710-28
– – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – – –
Synopsis
========
A vulnerability in Jython may lead to arbitrary code execution.
Background
==========
An implementation of Python written in Java.
Affected packages
=================
——————————————————————-
Package / Vulnerable / Unaffected
——————————————————————-
1 dev-java/jython < 2.7.0-r2 >= 2.7.0-r2
Description
===========
It was found that Jython is vulnerable to arbitrary code execution by
sending a serialized function to the deserializer.
Impact
======
Remote execution of arbitrary code by enticing a user to execute
malicious code.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Jython users should upgrade to the latest version:
# emerge –sync
# emerge –ask –oneshot –verbose “>=dev-java/jython-2.7.0-r2”
References
==========
[ 1 ] CVE-2016-4000
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4000
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201710-28
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users’ machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2017 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons – Attribution / Share Alike license.
http://creativecommons.org/licenses/by-sa/2.5—–BEGIN PGP SIGNATURE—–
iQEzBAABCAAdFiEEiDRK3jyVBE/RkymqpRQw84X1dt0FAln2DXEACgkQpRQw84X1
dt0Nhwf/T0gsKB5eyaqlH+GKOraDf9jxdGrM0DcrJMyzyNgDwfKn/h5K3tPXyaK7
ibbvbOanM77B+dD8+0+XwMb0IVaoUZ8K6h+S5Zn50LkLk58jVDDl+ycN69r1f8Fj
X0IwW+zZfuh8yZ2V7wibj+cSWSlrwCzEx5a/6TAo1hQ1ZliL3+wZZcoCHefRDcTV
7p3s5s3oGW6tpaCuY3YWsk8NzmK/TBFvpFXI4MT2qCbIOFnrOE2Bs0vZgvwKntYY
S3qxlN5ALzBQomfHv54fH2TqFsWqK5ncFdvXeAOYzZrgU3aix4i4CXNMR7D9olVY
Od0at5woptfyVKrSmxXx0LbhWome0w==
=sMwV
—–END PGP SIGNATURE—–