# CVE-2022-35413: Hardcoded credentials in n/a

> Attackers can use hardcoded credentials to access system configuration and confidential data like SSL keys via the web API.

- **Severity:** Critical 9.8 (`CVSS:3.1/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:** 13 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rwxr-7mfr-m8cg

## What is CVE-2022-35413?

CVE-2022-35413 is a critical vulnerability in n/a, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WAPPLES through 6.0 has a hardcoded systemi account. A threat actor could use this account to access the system configuration and confidential information (such as SSL keys) via an HTTPS request to the /webapi/ URI on port 443 or 5001.

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

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

It affects 1 product.


Products: Pentasecurity Wapples.

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

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

## Is CVE-2022-35413 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35413 exists.

Public exploit code:

- WAPPLES Web Application Firewall <=6.0 - Hardcoded Credentials (nuclei): http/cves/2022/CVE-2022-35413.yaml

## Other vulnerabilities in n/a

- [CVE-2022-35582](https://insights.sbomify.com/CVE-2022-35582/): Hardcoded credentials in n/a (high 8.8)
- [CVE-2022-31322](https://insights.sbomify.com/CVE-2022-31322/): Privilege escalation in n/a (high 7.8)
- [CVE-2022-31324](https://insights.sbomify.com/CVE-2022-31324/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-35413 is a critical vulnerability in n/a, published on 13 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-35413 exists.

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

## Sources

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

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