# CVE-2024-12839: Changing Information Technology CGFIDO - Authentication Bypass

> An attacker can bypass authentication in CGFIDO by capturing a signature from a forged website, allowing unauthorized system access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 31 Dec 2024
- **Updated:** 31 Dec 2024
- **Also known as:** GHSA-c45v-xc5j-qr2x

## What is CVE-2024-12839?

CVE-2024-12839 is a high-severity authentication bypass vulnerability in Changing Information Technology CGFIDO, published on 31 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The login mechanism via device authentication of CGFIDO from Changing Information Technology has an Authentication Bypass vulnerability. If a user visits a forged website, the agent program deployed on their device will send an authentication signature to the website. An unauthenticated remote attacker who obtains this signature can use it to log into the system with any device.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2024-12839?


## How do I fix CVE-2024-12839?

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

## Is CVE-2024-12839 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-12839 and fix it if it is affected.

What it is: CVE-2024-12839 is a high-severity authentication bypass vulnerability in Changing Information Technology CGFIDO, published on 31 Dec 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-12839 in the wild and no public exploit code.

Affected product: Changing Information Technology CGFIDO. 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-2024-12839/ (Markdown: https://insights.sbomify.com/CVE-2024-12839/index.md)
```

## Sources

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

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