# CVE-2013-5582: Auth bypass in n/a

> Local attackers can bypass authentication in Ammyy Admin by extracting the client ID from a fixed memory location in the executable.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ppfg-77qf-3457

## What is CVE-2013-5582?

CVE-2013-5582 is a high-severity authentication bypass vulnerability in n/a, published on 11 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Ammyy Admin 3.2 and earlier stores the client ID at a fixed memory location, which might make it easier for user-assisted remote attackers to bypass authentication by running a local program that extracts a field from the AA_v3.2.exe file.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2013-5582?

It affects 1 product.


Products: Ammyy Ammyy Admin.

## How do I fix CVE-2013-5582?

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

## Is CVE-2013-5582 being exploited?

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

Public exploit code:

- Ammyy Admin 3.2 - Authentication Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5582 and fix it if it is affected.

What it is: CVE-2013-5582 is a high-severity authentication bypass vulnerability in n/a, published on 11 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2013-5582 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-2013-5582/ (Markdown: https://insights.sbomify.com/CVE-2013-5582/index.md)
```

## Sources

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

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