Skip to content
Fencer Intel
critical 9.8

CVE-2011-4103 json

Django-piston and Django-tastypie do not properly deserialize YAML data

published 2014-10-27 12 y ago modified 2026-06-16 4 mo ago also GHSA-pvhp-v9qp-xf5r , PYSEC-2014-24 , EUVD-2014-0005

cvss
9.8
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
2.4%
EPSS 2.4% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

emitters.py in Django Piston before 0.2.3 and 0.2.x before 0.2.2.1 does not properly deserialize YAML data, which allows remote attackers to execute arbitrary Python code via vectors related to the yaml.load method.

Patch / fix

  • pypi django-piston 0.2.2.1, 0.2.3

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-2011-4103 updated cvss 6.8

django-piston: vulnerability in de-serialization of YAML post data could possibly allow remote execution or arbitrary code

  • 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

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

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi django-piston
>=0.2.0, <0.2.2.1
<0.2.3
0.2.2.1
0.2.3

Classification

Weakness
  • CWE-20 Improper Input Validation

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.