# CVE-2004-0939: Missing authorization in n/a

> Remote attackers can brute-force passwords in Neoteris IVE due to missing rate limiting on failed login attempts when LDAP or NT authentication is enabled.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 19 Nov 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xrq3-46cf-f7vr

## What is CVE-2004-0939?

CVE-2004-0939 is a medium-severity missing authorization vulnerability in n/a, published on 19 Nov 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

changepassword.cgi in Neoteris Instant Virtual Extranet (IVE) 3.x and 4.x, with LDAP authentication or NT domain authentication enabled, does not limit the number of times a bad password can be entered, which allows remote attackers to guess passwords via a brute force attack.

## Which versions are affected by CVE-2004-0939?

It affects 1 product.


Products: Neoteris Instant Virtual Extranet.

## How do I fix CVE-2004-0939?

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

## Is CVE-2004-0939 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0217](https://insights.sbomify.com/CVE-2003-0217/): Cross-site scripting in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0939 and fix it if it is affected.

What it is: CVE-2004-0939 is a medium-severity missing authorization vulnerability in n/a, published on 19 Nov 2004. 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-2004-0939 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-2004-0939/ (Markdown: https://insights.sbomify.com/CVE-2004-0939/index.md)
```

## Sources

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

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