CVE-2013-4315 json
Django Directory Traversal via ssi template tag
published 13y ago modified 4mo ago also GHSA-vjjp-9r83-22rc , PYSEC-2013-20 , EUVD-2013-0008
- cvss
- 8.6
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
Directory traversal vulnerability in Django 1.4.x before 1.4.7, 1.5.x before 1.5.3, and 1.6.x before 1.6 beta 3 allows remote attackers to read arbitrary files via a file path in the ALLOWED_INCLUDE_ROOTS setting followed by a .. (dot dot) in a ssi template tag.
Patch / fix
- pypi django 1.4.7, 1.5.3
- python-django Debian 14, Debian 13, Debian 12 1.5.3-1
debian advisories DEBIAN-CVE-2013-4315
- Django14 openstack 3 1.4.8-1.el6ost
red hat advisories RHSA-2013:1521
Is CVE-2013-4315 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2013-4315 updated cvss 2.1
python-django: directory traversal with "ssi" template tag
-
Red Hat OpenStack Platform 4 Django14affected: no fix available
-
Red Hat Subscription Asset Manager Djangoaffected: no fix planned “Will not fix”
-
Red Hat Enterprise Linux OpenStack Platform 3.0 Django14 1.4.8-1.el6ostfixed: vendor fix RHSA-2013:1521
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
3.27% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.1 | 8.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | django | >=1.4, <1.4.7 >=1.5, <1.5.3 |
1.4.7 1.5.3 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
djangoproject.com
/weblog/2013/sep/10/security-releases-issued/
patch, vendor-advisory, article
-
github.com
/django/django/commit/87d2750b39f6f2d54b7047225521a44dcd37e896
web
-
github.com
/django/django/commit/988b61c550d798f9a66d17ee0511fb7a9a7f33ca
web
-
lists.opensuse.org
/opensuse-updates/2013-10/msg00015.html
vendor-advisory, web
-
rhn.redhat.com
/errata/RHSA-2013-1521.html
vendor-advisory, web, advisory
-
debian.org
/security/2013/dsa-2755
vendor-advisory, web, advisory
-
secunia.com
/advisories/54772
third-party-advisory, vendor-advisory, advisory
-
secunia.com
/advisories/54828
third-party-advisory, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2013-4315
advisory
-
github.com
/django/django
package
-
github.com
/pypa/advisory-database/tree/main/vulns/django/PYSEC-2013-20.yaml
web
-
djangoproject.com
/weblog/2013/sep/10/security-releases-issued
web
-
github.com
/advisories/GHSA-vjjp-9r83-22rc
advisory
Sources
- CVE List CVE-2013-4315
- GitHub Advisory GHSA-vjjp-9r83-22rc
- NVD CVE-2013-4315
- OSV PYSEC-2013-20
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.