Bug 726426 (CVE-2011-2923, CVE-2011-2924)
Summary: | CVE-2011-2923 CVE-2011-2924 foomatic: foomatic-rip (debug mode) insecure temporary file use in renderer command line by processing PostScript data | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Jan Lieskovsky <jlieskov> |
Component: | vulnerability | Assignee: | Red Hat Product Security <security-response-team> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | unspecified | CC: | jpopelka, twaugh |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-08-22 15:19:08 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 726432 | ||
Bug Blocks: |
Description
Jan Lieskovsky
2011-07-28 14:49:45 UTC
This issue affects the versions of the foomatic package, as shipped with Red Hat Enterprise Linux 4, 5, and 6. -- This issue affects the versions of the foomatic package, as shipped with Fedora release of 14 and 15. Please schedule an update. CVE Request: [1] http://www.openwall.com/lists/oss-security/2011/07/28/9 Created foomatic tracking bugs for this issue Affects: fedora-all [bug 726432] Two CVEs have been assigned to this issue: CVE-2011-2923 for the perl variant. CVE-2011-2924 for the C variant. Reference: http://thread.gmane.org/gmane.comp.security.oss.general/5615/focus=5725 There's this in foomaticrip.c as well: if (debug) logh = fopen(LOG_FILE ".log", "w"); /* insecure, use for debugging only */ Reported upstream: http://bugs.linux-foundation.org/show_bug.cgi?id=936 Statement: Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/. |