# CVE-2013-1867: Path traversal in Gemalto Tokend

> An attacker can create or overwrite arbitrary files in Gemalto Tokend, potentially leading to privilege escalation or data modification.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f62q-ww86-h898

## What is CVE-2013-1867?

CVE-2013-1867 is a medium-severity path traversal vulnerability in Gemalto Tokend, published on 30 Jan 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Gemalto Tokend 2013 has an Arbitrary File Creation/Overwrite Vulnerability

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

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

It affects 1 product.


Products: Apple Tokend.

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

No fix has been published for CVE-2013-1867 yet. Limit exposure of the affected software until one is available.

## Is CVE-2013-1867 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2013-1867 is a medium-severity path traversal vulnerability in Gemalto Tokend, published on 30 Jan 2020. 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-1867 in the wild and no public exploit code.

Affected product: Gemalto Tokend. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-1867/ (Markdown: https://insights.sbomify.com/CVE-2013-1867/index.md)
```

## Sources

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

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