# CVE-2013-2217: Improper Link Resolution Before File Access in Suds

> Local attackers can exploit a symlink vulnerability in Suds cache files to redirect SOAP queries or cause unspecified impacts.

- **Severity:** Low 1.2 (`AV:L/AC:H/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-2217, GHSA-vpqp-hx68-p2wx, MGASA-2013-0224, PYSEC-2013-32, PYSEC-2013-33, SUSE-SU-2016:2704-1, openSUSE-SU-2024:10144-1, openSUSE-SU-2024:11275-1, openSUSE-SU-2024:11578-1, openSUSE-SU-2024:12127-1, openSUSE-SU-2025:15105-1

## What is CVE-2013-2217?

CVE-2013-2217 is a low-severity path traversal vulnerability in Opensuse Opensuse, published on 23 Sep 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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/.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2013-2217?

6 open source packages ship an affected version, including suds and suds-py3. It affects 3 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `suds` | PyPI | All versions | 0.7.0 |
| `suds` | PyPI | All versions | 1.0.0 |
| `suds` | PyPI | All versions | 1.0.0 |
| `suds-py3` | PyPI | All versions | 1.4.4.1 |
| `suds-py3` | PyPI | All versions | 1.4.4.1 |
| `suds-py3` | PyPI | All versions | 1.4.4.1 |
| `python-suds-jurko` | SUSE:OpenStack Cloud 6 | All versions | 0.6-4.1 |
| `python-suds` | openSUSE:Tumbleweed | All versions | 1.2.0-2.4 |
| `python-suds-community` | openSUSE:Tumbleweed | All versions | 0.8.5-1.1 |
| `python-suds-jurko` | openSUSE:Tumbleweed | All versions | 0.6-4.1 |

Products: Jeff Ortel Suds, Opensuse Opensuse, Redhat Enterprise Linux.

## How do I fix CVE-2013-2217?

Upgrade suds to a fixed version for your release line: 0.7.0 or 1.0.0.

## Is CVE-2013-2217 being exploited?

There is no known exploitation of CVE-2013-2217 in the wild and no public exploit code.

Public exploit code:

-  Clone of suds 0.4 + suds-0.4-CVE-2013-2217.patch (github_poc): https://github.com/Osirium/suds

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-2217 and fix it if it is affected.

What it is: CVE-2013-2217 is a low-severity path traversal vulnerability in Opensuse Opensuse, published on 23 Sep 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-2217 in the wild and no public exploit code.

Affected packages and fixed versions:
- suds (PyPI): affected all versions; fixed in 0.7.0
- suds (PyPI): affected all versions; fixed in 1.0.0
- suds (PyPI): affected all versions; fixed in 1.0.0
- suds-py3 (PyPI): affected all versions; fixed in 1.4.4.1
- suds-py3 (PyPI): affected all versions; fixed in 1.4.4.1
- suds-py3 (PyPI): affected all versions; fixed in 1.4.4.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-2217/ (Markdown: https://insights.sbomify.com/CVE-2013-2217/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-2217
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-2217
- OSV: https://osv.dev/vulnerability/CVE-2013-2217

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-2217/
Summaries are generated and may contain mistakes; the official description above is the record.