dbcve.org
E Document SystemApplication · Eic

CVE-2021-34683

MEDIUM · 5.3 CVSS v3.1 Published 2021-06-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The EIC E-document System 3.0 contains an unauthenticated information disclosure vulnerability in the endpoint kw/auth/bbs/asp/get_user_email_info_bbs.asp. This endpoint exposes the names and email addresses of all users in the organization without requiring authentication, effectively revealing the entire organization's contact directory to any remote attacker.

MitigationImplement proper authentication and authorization checks on the affected endpoint to restrict access to authorized users only. Additionally, implement rate limiting, account lockout policies, and CAPTCHA on login pages to mitigate brute force attacks enabled by the exposed credential information.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
E Document SystemApplication
Affected:= 3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Eic E Document System 3.0 is installed
    Inspect the web server's installed applications or check the application directory for 'Eic E Document System' or 'eic' with version 3.0. Check the application banner or about page if available.
    Affected if The application is Eic E Document System version 3.0
  2. Check if the vulnerable endpoint exists
    Make an HTTP GET request to /kw/auth/bbs/asp/get_user_email_info_bbs.asp on the web server hosting the application.
    Affected if The endpoint responds with any HTTP status code (200, 404, 500, etc.), indicating the file exists and is reachable
  3. Verify if the endpoint requires authentication
    Send an HTTP request to the vulnerable endpoint without providing any authentication credentials (no cookies, no Basic Auth, no session token). Observe the response to determine if access is granted without credentials.
    Affected if The endpoint returns a successful response (HTTP 200) without requiring any authentication headers or session cookies
  4. Check if user email information is exposed
    Examine the HTTP response body from the unauthenticated request to the endpoint. Look for patterns containing email addresses (e.g., [email protected]) and user names.
    Affected if The response contains a list of user names paired with email addresses from the organization without any authentication requirement
  5. Confirm full directory exposure
    Compare the number of user records returned by the endpoint against the expected user count in the organization. The vulnerability exposes the entire contact directory.
    Affected if The endpoint returns email addresses for all or most users in the organization, revealing the complete internal contact directory

A defender is affected if Eic E Document System 3.0 is running and the /kw/auth/bbs/asp/get_user_email_info_bbs.asp endpoint returns user names and email addresses without requiring any authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks on the affected endpoint to restrict access to authorized users only. Additionally, implement rate limiting, account lockout policies, and CAPTCHA on login pages to mitigate brute force attacks enabled by the exposed credential information.

Fix this in E Document System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-34683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-34683 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data