# CVE-2021-41995: PingID Mac Login prior to 1.1 vulnerable to pre-computed dictionary attacks

> Attackers can bypass Multi-Factor Authentication in PingID Mac Login via pre-computed dictionary attacks due to RSA misconfiguration.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cvx4-2j8v-rqmj

## What is CVE-2021-41995?

CVE-2021-41995 is a high-severity vulnerability in PingID Mac Login, published on 30 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A misconfiguration of RSA in PingID Mac Login prior to 1.1 is vulnerable to pre-computed dictionary attacks, leading to an offline MFA bypass.

Weakness: CWE-287 (Improper Authentication), CWE-310, CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2021-41995?

It affects 1 product.


Products: Pingidentity Pingid Integration for Mac Login.

## How do I fix CVE-2021-41995?

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

## Is CVE-2021-41995 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41995 and fix it if it is affected.

What it is: CVE-2021-41995 is a high-severity vulnerability in PingID Mac Login, published on 30 Jun 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41995 in the wild and no public exploit code.

Affected product: PingID Mac Login. 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-2021-41995/ (Markdown: https://insights.sbomify.com/CVE-2021-41995/index.md)
```

## Sources

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

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