# CVE-2016-7490: Path traversal in Studio Express

> A local attacker can exploit insecure temporary file handling during installation to overwrite system files or escalate privileges via symlink attacks.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9wgq-3542-p7cg

## What is CVE-2016-7490?

CVE-2016-7490 is a high-severity path traversal vulnerability in Teradata Studio Express, published on 10 Nov 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The installation script studioexpressinstall for Teradata Studio Express 15.12.00.00 creates files in /tmp insecurely. A malicious local user could create a symlink in /tmp and possibly clobber system files or perhaps elevate privileges.

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

## Which versions are affected by CVE-2016-7490?

It affects 1 product.


Products: Teradata Studio Express.

## How do I fix CVE-2016-7490?

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

## Is CVE-2016-7490 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7490 and fix it if it is affected.

What it is: CVE-2016-7490 is a high-severity path traversal vulnerability in Teradata Studio Express, published on 10 Nov 2016. 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-2016-7490 in the wild and no public exploit code.

Affected product: Teradata Studio Express. 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-2016-7490/ (Markdown: https://insights.sbomify.com/CVE-2016-7490/index.md)
```

## Sources

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

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