# CVE-2022-30076: Information disclosure in n/a

> Attackers can enumerate user full names by brute-forcing student usernames due to missing rate limiting in ENTAB ERP.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2023
- **Updated:** 6 Feb 2025
- **Also known as:** GHSA-g7h3-m79w-rcrp

## What is CVE-2022-30076?

CVE-2022-30076 is a medium-severity vulnerability in n/a, published on 16 Apr 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ENTAB ERP 1.0 allows attackers to discover users' full names via a brute force attack with a series of student usernames such as s10000 through s20000. There is no rate limiting.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Entab Erp.

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

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

## Is CVE-2022-30076 being exploited?

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

Public exploit code:

- ENTAB ERP 1.0 - Username PII leak (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-30076 is a medium-severity vulnerability in n/a, published on 16 Apr 2023. 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-30076 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-30076/ (Markdown: https://insights.sbomify.com/CVE-2022-30076/index.md)
```

## Sources

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

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