# CVE-2018-3743: Open Redirect in hekto

> An open redirect vulnerability in the hekto npm library allows attackers to redirect users to malicious sites when specific filenames are used.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qmm9-x5gr-4gfm

## What is CVE-2018-3743?

CVE-2018-3743 is a medium-severity vulnerability in HackerOne hekto, published on 1 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Open redirect in hekto <=0.2.3 when target domain name is used as html filename on server.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2018-3743?

2 open source packages ship an affected version, including hekto. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hekto` | npm | All versions | 0.2.4 |
| `hekto` | npm | All versions | 0.2.4 |

Products: Hekto Project Hekto.

## How do I fix CVE-2018-3743?

Upgrade hekto to 0.2.4 or later.

## Is CVE-2018-3743 being exploited?

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

## Other vulnerabilities in HackerOne hekto

- [CVE-2018-3725](https://insights.sbomify.com/CVE-2018-3725/): Path Traversal in hekto (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-3743 and fix it if it is affected.

What it is: CVE-2018-3743 is a medium-severity vulnerability in HackerOne hekto, published on 1 Jun 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-3743 in the wild and no public exploit code.

Affected packages and fixed versions:
- hekto (npm): affected all versions; fixed in 0.2.4
- hekto (npm): affected all versions; fixed in 0.2.4

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

## Sources

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

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