# CVE-2002-0712: Security feature bypass in n/a

> A master user can bypass multi-user authorization requirements to perform restricted operations in Entrust Authority Security Manager.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-g4m2-r9hq-hpqq

## What is CVE-2002-0712?

CVE-2002-0712 is a low-severity vulnerability in n/a, published on 14 Jan 2004. 

### Official description

Entrust Authority Security Manager (EASM) 6.0 does not properly require multiple master users to change the password of a master user, which could allow a master user to perform operations that require multiple authorizations.

## Which versions are affected by CVE-2002-0712?

It affects 1 product.


Products: Entrust Entrust Authority Security Manager.

## How do I fix CVE-2002-0712?

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

## Is CVE-2002-0712 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0712 and fix it if it is affected.

What it is: CVE-2002-0712 is a low-severity vulnerability in n/a, published on 14 Jan 2004. 
Exploitation: There is no known exploitation of CVE-2002-0712 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-2002-0712/ (Markdown: https://insights.sbomify.com/CVE-2002-0712/index.md)
```

## Sources

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

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