# CVE-2022-30421: Auth bypass in n/a

> An improper authentication flaw in Toshiba Storage Security Software allows local attackers to bypass password checks and obtain sensitive information.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jan 2023
- **Updated:** 27 Mar 2025

## What is CVE-2022-30421?

CVE-2022-30421 is a high-severity authentication bypass vulnerability in n/a, published on 31 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper Authentication vulnerability in Toshiba Storage Security Software V1.2.0.7413 is that allows for sensitive information to be obtained via(local) password authentication module.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Toshiba Storage Security Software.

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

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

## Is CVE-2022-30421 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30421 is a high-severity authentication bypass vulnerability in n/a, published on 31 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-30421 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-30421/ (Markdown: https://insights.sbomify.com/CVE-2022-30421/index.md)
```

## Sources

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

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