# CVE-2017-7462: Hardcoded credentials in n/a

> A vendor backdoor in the Intellinet IP Camera allows remote attackers to access sensitive CGI scripts via hardcoded credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mm84-q6xw-wq6x

## What is CVE-2017-7462?

CVE-2017-7462 is a critical vulnerability in n/a, published on 11 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Intellinet NFC-30ir IP Camera has a vendor backdoor that can allow a remote attacker access to a vendor-supplied CGI script in the web directory.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Intellinet-Network Nfc-30ir Firmware.

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

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

## Is CVE-2017-7462 being exploited?

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

Public exploit code:

- Intellinet NFC-30IR Camera - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-7461](https://insights.sbomify.com/CVE-2017-7461/): Path traversal in n/a (medium 4.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-7462 is a critical vulnerability in n/a, published on 11 Apr 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-7462 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-7462/ (Markdown: https://insights.sbomify.com/CVE-2017-7462/index.md)
```

## Sources

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

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