CVE-2013-2217: cache.py in Suds 0.4, when tempdir is set to None, allows local users to redirect SOAP queries and possibly have other unspecified impact…
Noroxi assessment
Priority: Monitor (action score 4/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
- Special conditions such as timing or configuration are required.
- Fixed version: suds (Debian:12) 0.4.1-8; python-suds (openSUSE:Tumbleweed) 1.2.0-2.4; python-suds-community (openSUSE:Tumbleweed) 0.8.5-1.1.
Low priority for now. Upgrade to suds (Debian:12) 0.4.1-8; python-suds (openSUSE:Tumbleweed) 1.2.0-2.4; python-suds-community (openSUSE:Tumbleweed) 0.8.5-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
cache.py in Suds 0.4, when tempdir is set to None, allows local users to redirect SOAP queries and possibly have other unspecified impact via a symlink attack on a cache file with a predictable name in /tmp/suds/.
- Published
- Sep 23, 2013
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 47th percentile
- CWE
- CWE-59
Report tools
Action score
4
Low priority for now.
- CVSS
- 4 / 40 · 1.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jeff ortel | suds | cpe:2.3:a:jeff_ortel:suds |
| opensuse | opensuse | cpe:2.3:o:opensuse:opensuse |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jeff ortel suds0.4
- opensuse opensuse12.2
- opensuse opensuse12.3
- redhat enterprise linux5
- redhat enterprise linux6.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | suds | before 0.4.1-8 | 0.4.1-8 |
| openSUSE:Tumbleweed | python-suds | before 1.2.0-2.4 | 1.2.0-2.4 |
| openSUSE:Tumbleweed | python-suds-community | before 0.8.5-1.1 | 0.8.5-1.1 |
| openSUSE:Tumbleweed | python-suds-jurko | before 0.6-4.1 | 0.6-4.1 |
| PyPI | suds | before 1.0.0 | 1.0.0 |
| PyPI | suds | before 0.7.0 | 0.7.0 |
| PyPI | suds-py3 | before 1.4.4.1 | 1.4.4.1 |
| SUSE:OpenStack Cloud 6 | python-suds-jurko | before 0.6-4.1 | 0.6-4.1 |
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:suds | 0.4.1-8 · Debian:12 | Package registry (OSV) |
| opensuse:python-suds | 1.2.0-2.4 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-suds-community | 0.8.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:python-suds-jurko | 0.6-4.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:suds | 0.7.0 | Package registry (OSV) |
| PyPI:suds | 1.0.0 | Package registry (OSV) |
| PyPI:suds-py3 | 1.4.4.1 | Package registry (OSV) |
| suse:python-suds-jurko | 0.6-4.1 · SUSE:OpenStack Cloud 6 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2018-02-22 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+1612 d
- TodayNov 16, 2026+4802 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- High
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
AV:L/AC:H/Au:N/C:N/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.