# CVE-2013-7293: Misconfiguration in n/a

> Remote attackers can hijack router configuration traffic by controlling the DNS hostname advised in documentation, bypassing security controls.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** No
- **Published:** 15 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6xxp-p3pp-qrxg

## What is CVE-2013-7293?

CVE-2013-7293 is a medium-severity vulnerability in n/a, published on 15 Jan 2014. 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

The ASUS WL-330NUL router has a configuration process that relies on accessing the 192.168.1.1 IP address, but the documentation advises users to instead access a DNS hostname that does not always resolve to 192.168.1.1, which makes it easier for remote attackers to hijack the configuration traffic by controlling the server associated with that hostname.

Weakness: CWE-284 (Improper Access Control), CWE-16

## Which versions are affected by CVE-2013-7293?

It affects 1 product.


Products: Asus Wl-330nul.

## How do I fix CVE-2013-7293?

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

## Is CVE-2013-7293 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-7789](https://insights.sbomify.com/CVE-2015-7789/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-7293 and fix it if it is affected.

What it is: CVE-2013-7293 is a medium-severity vulnerability in n/a, published on 15 Jan 2014. 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-2013-7293 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-2013-7293/ (Markdown: https://insights.sbomify.com/CVE-2013-7293/index.md)
```

## Sources

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

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