# CVE-2023-6329: Control iD iDSecure passwordCustom Authentication Bypass

> An unauthenticated attacker can bypass authentication in Control iD iDSecure to gain administrative privileges via a flawed login routine.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 27 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9jjv-7crp-6rr2

## What is CVE-2023-6329?

CVE-2023-6329 is a critical authentication bypass vulnerability in Control iD iDSecure, published on 27 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability exists in Control iD iDSecure v4.7.32.0. The login routine used by iDS-Core.dll contains a "passwordCustom" option that allows an unauthenticated attacker to compute valid credentials that can be used to bypass authentication and act as an administrative user.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-6329?

It affects 1 product.


Products: Controlid Idsecure.

## How do I fix CVE-2023-6329?

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

## Is CVE-2023-6329 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6329 exists.

Public exploit code:

- CVE-2023-6329 – Authentication bypass PoC for Control iD iDSecure ≤ 4.7.43.0 (github_poc): https://github.com/itzvenom/CVE-2023-6329
- Control iD iDSecure Authentication Bypass (CVE-2023-6329) (metasploit)
- Control iD iDSecure - Authentication Bypass (nuclei): http/cves/2023/CVE-2023-6329.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6329 and fix it if it is affected.

What it is: CVE-2023-6329 is a critical authentication bypass vulnerability in Control iD iDSecure, published on 27 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-6329 exists.

Affected product: Control iD iDSecure. 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-2023-6329/ (Markdown: https://insights.sbomify.com/CVE-2023-6329/index.md)
```

## Sources

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

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