# CVE-2014-1644: Auth bypass in n/a

> Remote attackers can reset arbitrary user passwords via the forgotten-password feature, leading to account takeover.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h5j2-74f6-pf8w

## What is CVE-2014-1644?

CVE-2014-1644 is a high-severity authentication bypass vulnerability in n/a, published on 29 Mar 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The forgotten-password feature in forcepasswd.do in the management GUI in Symantec LiveUpdate Administrator (LUA) 2.x before 2.3.2.110 allows remote attackers to reset arbitrary passwords by providing the e-mail address associated with a user account.

Weakness: CWE-255

## Which versions are affected by CVE-2014-1644?

It affects 1 product.


Products: Symantec Liveupdate Administrator.

## How do I fix CVE-2014-1644?

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

## Is CVE-2014-1644 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-1645](https://insights.sbomify.com/CVE-2014-1645/): SQL injection in n/a (high 7.5)
- [CVE-2012-0304](https://insights.sbomify.com/CVE-2012-0304/): Privilege escalation in n/a (medium 6.9)
- [CVE-2011-0545](https://insights.sbomify.com/CVE-2011-0545/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2011-1524](https://insights.sbomify.com/CVE-2011-1524/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1644 and fix it if it is affected.

What it is: CVE-2014-1644 is a high-severity authentication bypass vulnerability in n/a, published on 29 Mar 2014. 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-2014-1644 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-2014-1644/ (Markdown: https://insights.sbomify.com/CVE-2014-1644/index.md)
```

## Sources

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

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