CVE-2013-2027: Medium severity suse linux vulnerability

Published Apr 3, 2013
·
Updated

Description of problem:

There are serveral problems with the way Jython creates class cache files, potentially leading to arbitrary code execution or information disclosure.

(umask 000; jython -c 'import xmllib') ls -l '/usr/share/jython/Lib/xmllib$py.class' -rw-rw-rw-. 1 root root 52874 Apr 3 17:24 /usr/share/jython/Lib/xmllib$py.class

Jython does not explicitly set permissions of the class files; therefore with weak umask it creates world-writable files, or discloses sensitive data that would be in a non-world-readable package file.

Also, the package writes to /usr/share, which it shouldn't; /var/cache would be more appropriate, but would still lead to a possibility of a content disclosure.

The only really portable and secure way to cache class files would be a directory in user's home with 0700 permissions.

It is currently even not possible to easily disable the caching, since the configuration file is not marked with %config and resides in /usr/share instead of /etc.

Version-Release number of selected component (if applicable):

jython-2.2.1-4.8.el6.x8664

Other sources

Jython 2.2.1 uses the current umask to set the privileges of the class cache files, which allows local users to bypass intended access restrictions via unspecified vectors.

MITRE

Jython before 2.7.2b3 uses the current umask to set the privileges of the class cache files, which allows local users to bypass intended access restrictions via unspecified vectors.

Affected Software

4 affected componentsFixes available
maven/org.python:jython-standalone<2.7.2b3
2.7.2b3
openSUSE openSUSE=13.1
openSUSE openSUSE=13.2
Jython Project Jython=2.2.1

Event History

Apr 3, 2013
Data Sourced
via Red Hat·03:29 PM
DescriptionSeverityAffected Software
Feb 13, 2015
CVE Published
via MITRE·03:00 PM
Data Sourced
via MITRE·03:00 PM
Description
May 14, 2022
Advisory Published
02:05 AM

Frequently Asked Questions

1

What is the severity of CVE-2013-2027?

CVE-2013-2027 is classified as a high severity vulnerability due to potential arbitrary code execution and information disclosure.

2

How do I fix CVE-2013-2027?

To fix CVE-2013-2027, upgrade Jython to version 2.7.2b3 or later to mitigate the risks associated with this vulnerability.

3

What software is affected by CVE-2013-2027?

CVE-2013-2027 affects Jython versions prior to 2.7.2b3, specifically on platforms such as openSUSE 13.1 and 13.2.

4

What are the potential risks of CVE-2013-2027?

The potential risks of CVE-2013-2027 include arbitrary code execution and exposure of sensitive information.

5

Is CVE-2013-2027 related to Jython's class cache files?

Yes, CVE-2013-2027 arises from issues in how Jython creates class cache files, leading to serious security implications.

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