# CVE-2022-26672: ASUS WebStorage - Use of Hard-coded Credentials

> An attacker can use a hardcoded API token to bypass authentication and access, modify, or delete user account data in ASUS WebStorage.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qr5q-3r8x-rmr4

## What is CVE-2022-26672?

CVE-2022-26672 is a high-severity vulnerability in ASUS WebStorage, published on 22 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ASUS WebStorage has a hardcoded API Token in the APP source code. An unauthenticated remote attacker can use this token to establish connections with the server and carry out login attempts to general user accounts. A successful login to a general user account allows the attacker to access, modify or delete this user account information.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2022-26672?

It affects 1 product.


Products: Asus Webstorage.

## How do I fix CVE-2022-26672?

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

## Is CVE-2022-26672 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26672 and fix it if it is affected.

What it is: CVE-2022-26672 is a high-severity vulnerability in ASUS WebStorage, published on 22 Apr 2022. 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-2022-26672 in the wild and no public exploit code.

Affected product: ASUS WebStorage. 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-2022-26672/ (Markdown: https://insights.sbomify.com/CVE-2022-26672/index.md)
```

## Sources

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

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