Skip to content
Fencer Intel
low 3.6

CVE-2012-2451 json

The Config::IniFiles module before 2.71 for Perl creates temporary files with predictable names, which allows local users to overwrite arbi…

published 2012-06-27 14 y ago modified 2026-06-16 4 mo ago also EUVD-2012-2437

cvss
3.6
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 43%
public exploits
0
none known

Summary

The Config::IniFiles module before 2.71 for Perl creates temporary files with predictable names, which allows local users to overwrite arbitrary files via a symlink attack. NOTE: some of these details are obtained from third party information. NOTE: it has been reported that this might only be exploitable by writing in the same directory as the .ini file. If this is the case, then this issue might not cross privilege boundaries.

Patch / fix

  • libconfig-inifiles-perl Debian 14, Debian 13, Debian 12 2.72-1

debian advisories DEBIAN-CVE-2012-2451

  • perl-Config-IniFiles openSUSE Tumbleweed 2.94-1.1

opensuse advisories openSUSE-SU-2024:10146-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-2451 updated cvss 1.9

perl-Config-IniFiles: insecure temporary file usage

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • bitbucket.org https://bitbucket.org/shlomif/perl-config-inifiles/changeset/a08fa26f4f59 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 3.6 AV:L/AC:L/Au:N/C:N/I:P/A:P

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.