Skip to content
Fencer Intel
medium 6.0

CVE-2015-5242 json

OpenStack Swift-on-File (aka Swiftonfile) does not properly restrict use of the pickle Python module when loading metadata, which allows re…

published 10y ago modified 4mo ago also EUVD-2015-5235

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

Summary

OpenStack Swift-on-File (aka Swiftonfile) does not properly restrict use of the pickle Python module when loading metadata, which allows remote authenticated users to execute arbitrary code via a crafted extended attribute (xattrs).

Patch / fix

  • swiftonfile storage 3.1 1.13.1-6.el6rhs
  • swiftonfile storage 3.1 1.13.1-6.el7rhgs

red hat advisories RHSA-2015:1918

Is CVE-2015-5242 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2015-5242 updated cvss 6.0

swiftonfile: use of insecure Python pickle for metadata serialization and storage

  • Red Hat Gluster Storage Server 3.1 on RHEL-6 swiftonfile 1.13.1-6.el6rhs Red Hat Gluster Storage Server 3.1 on RHEL-7 swiftonfile 1.13.1-6.el7rhgs
    fixed: vendor fix RHSA-2015:1918

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

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

CVSS scores

assigned by version score vector
NVD 2.0 6.0 AV:N/AC:M/Au:S/C:P/I:P/A:P

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

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.