# CVE-2017-14147: Auth bypass in n/a

> An attacker can bypass authentication to reset a FiberHome router to factory settings, enabling login with default 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:** 7 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-f5q6-j72g-m599

## What is CVE-2017-14147?

CVE-2017-14147 is a critical authentication bypass vulnerability in n/a, published on 7 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on FiberHome User End Routers Bearing Model Number AN1020-25 which could allow an attacker to easily restore a router to its factory settings by simply browsing to the link http://[Default-Router-IP]/restoreinfo.cgi & execute it. Due to improper authentication on this page, the software accepts the request hence allowing attacker to reset the router to its default configurations which later could allow attacker to login to router by using default username/password.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Fiberhome Adsl An1020-25 Firmware.

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

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

## Is CVE-2017-14147 being exploited?

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

Public exploit code:

- FiberHome ADSL AN1020-25 - Improper Access Restrictions (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-14147 is a critical authentication bypass vulnerability in n/a, published on 7 Sep 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-14147 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-14147/ (Markdown: https://insights.sbomify.com/CVE-2017-14147/index.md)
```

## Sources

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

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