# CVE-2021-34683: Information disclosure in n/a

> Remote attackers can access all organizational contact information via an exposed ASP endpoint, facilitating social engineering and brute force attacks.

- **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 Jun 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2xv4-x724-2399

## What is CVE-2021-34683?

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

### Official description

An issue was discovered in EXCELLENT INFOTEK CORPORATION (EIC) E-document System 3.0. A remote attacker can use kw/auth/bbs/asp/get_user_email_info_bbs.asp to obtain the contact information (name and e-mail address) of everyone in the entire organization. This information can allow remote attackers to perform social engineering or brute force attacks against the system login page.

## Which versions are affected by CVE-2021-34683?

It affects 1 product.


Products: Eic E-Document System.

## How do I fix CVE-2021-34683?

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

## Is CVE-2021-34683 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-22859](https://insights.sbomify.com/CVE-2021-22859/): EIC e-document system - SQL Injection (critical 9.8)
- [CVE-2021-22860](https://insights.sbomify.com/CVE-2021-22860/): EIC e-document system - Broken Authentication (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-34683 and fix it if it is affected.

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

## Sources

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

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