# CVE-2017-7444: Other in n/a

> Attackers with directory write access can execute arbitrary code via DLL hijacking in the patch installer of Veritas System Recovery.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-755f-qgr8-28qg

## What is CVE-2017-7444?

CVE-2017-7444 is a high-severity vulnerability in n/a, published on 5 Apr 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

In Veritas System Recovery before 16 SP1, there is a DLL hijacking vulnerability in the patch installer if an attacker has write access to the directory from which the product is executed.

## Which versions are affected by CVE-2017-7444?

It affects 1 product.


Products: Veritas System Recovery.

## How do I fix CVE-2017-7444?

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

## Is CVE-2017-7444 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-36160](https://insights.sbomify.com/CVE-2020-36160/): Path traversal in n/a (critical 9.3)
- [CVE-2022-41320](https://insights.sbomify.com/CVE-2022-41320/): Information disclosure in n/a (medium 6.5)
- [CVE-2022-26778](https://insights.sbomify.com/CVE-2022-26778/): Information disclosure in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7444 and fix it if it is affected.

What it is: CVE-2017-7444 is a high-severity vulnerability in n/a, published on 5 Apr 2017. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-7444 in the wild and no public exploit code.

Affected product: n/a. 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-2017-7444/ (Markdown: https://insights.sbomify.com/CVE-2017-7444/index.md)
```

## Sources

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

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