Bug 1284922 - perl-IPTables-Parse: insecure temporary file use
perl-IPTables-Parse: insecure temporary file use
Status: CLOSED DUPLICATE of bug 1267962
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20151124,reported=2...
: Security
Depends On: 1284924 1267963 1284923
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-24 08:18 EST by Martin Prpič
Modified: 2015-11-24 08:49 EST (History)
4 users (show)

See Also:
Fixed In Version: IPTables-Parse 1.6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-24 08:49:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Prpič 2015-11-24 08:18:52 EST
A flaw was fixed in perl-IPTables-Parse:

(Miloslav Trmač) Fixed a vulnerability to not use predictable names for temporary files. This vulnerability would allow an attacker on a multi- user system to set up symlinks to overwrite any file the current user has write access to. If a user manually overrides the temporary file locations with the 'iptout' and 'ipterr' hash keys, it is recommended to not use predictable names either.

CVE request:

http://seclists.org/oss-sec/2015/q4/366

Upstream patch:

https://github.com/mtrmac/IPTables-Parse/commit/b400b976d81140f6971132e94eb7657b5b0a2b87

External References:

https://metacpan.org/source/MRASH/IPTables-Parse-1.6/Changes#L3
Comment 1 Martin Prpič 2015-11-24 08:19:17 EST
Created perl-IPTables-Parse tracking bugs for this issue:

Affects: fedora-all [bug 1284923]
Affects: epel-all [bug 1284924]
Comment 2 Miloslav Trmač 2015-11-24 08:27:16 EST
This is already #1267962, isn’t it?
Comment 3 Martin Prpič 2015-11-24 08:49:22 EST
(In reply to Miloslav Trmač from comment #2)
> This is already #1267962, isn’t it?

Bah, you're right. Sorry about that. Thanks for closing all of these.

*** This bug has been marked as a duplicate of bug 1267962 ***

Note You need to log in before you can comment on or make changes to this bug.