CVE-2009-0318: Medium severity Gnome Gnumeric vulnerability

Published Aug 6, 2008
·
Updated

Untrusted search path vulnerability in the GObject Python interpreter wrapper in Gnumeric allows local users to execute arbitrary code via a Trojan horse Python file in the current working directory, related to a vulnerability in the PySysSetArgv function (CVE-2008-5983).

Other sources

Untrusted search path vulnerability in the GObject wrapper around Python interpreter allows local users to execute arbitrary code via a Trojan horse Python file in the current working directory, related to an erroneous setting of sys.path by the PySysSetArgv function.

References (more details, test case): http://www.nabble.com/Bug-484305%3A-bicyclerepair%3A-bike.vim-imports-untrusted-python-files-from-cwd-td18848099.html

Relevant part of the code in gnumeric-N.V.R/plugins/python-loader/gnm-py-interpreter.c:

103 PySysSetArgv (GNELEMENTS (pluginargv) - 1, pluginargv); 104 pyinitgnumeric (interpreter);

Proposed patch: The Debian patch for similar dia's Python related issue, available at:

http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=5;filename=pythonpath.diff;att=1;bug=504251

should be sufficient to resolve this issue.

Red Hat

Affected Software

1 affected component
Gnome Gnumeric

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch pythonpath.diff
  2. Configuration

    Modify the PySys_SetArgv call in gnm-py-interpreter.c so that it sets sys.path and does not include the current working directory (prevent importing untrusted Python files from cwd).

    gnumeric-N.V.R/plugins/python-loader/gnm-py-interpreter.c sys.path (via PySys_SetArgv) = exclude current working directory

Event History

Aug 6, 2008
CVE Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionSeverity
Jan 26, 2009
Data Sourced
via Red Hat·02:18 PM
Affected Software
Jan 28, 2009
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description
Data Sourced
via NVD·11:30 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2009-0318?

CVE-2009-0318 is classified as a medium severity vulnerability due to its ability to allow local users to execute arbitrary code.

2

How do I fix CVE-2009-0318?

To fix CVE-2009-0318, ensure that you update Gnumeric to the latest version that addresses this vulnerability.

3

Who is affected by CVE-2009-0318?

CVE-2009-0318 affects local users of the Gnumeric application in environments where untrusted Python files are present.

4

What type of vulnerability is CVE-2009-0318?

CVE-2009-0318 is an untrusted search path vulnerability that can lead to the execution of arbitrary code.

5

When was CVE-2009-0318 published?

CVE-2009-0318 was published on February 9, 2009.

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