# CVE-2023-33371: Hardcoded credentials in n/a

> Attackers can bypass authentication and take over accounts by exploiting a hardcoded cryptographic key used for signing JWT session tokens in IDSecure.

- **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:** 3 Aug 2023
- **Updated:** 17 Oct 2024
- **Also known as:** GHSA-624m-rx55-7pqf

## What is CVE-2023-33371?

CVE-2023-33371 is a critical vulnerability in n/a, published on 3 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Control ID IDSecure 4.7.26.0 and prior uses a hardcoded cryptographic key in order to sign and verify JWT session tokens, allowing attackers to sign arbitrary session tokens and bypass authentication.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Assaabloy Control Id Idsecure.

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

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

## Is CVE-2023-33371 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-33367](https://insights.sbomify.com/CVE-2023-33367/): SQL injection in n/a (critical 9.8)
- [CVE-2025-49853](https://insights.sbomify.com/CVE-2025-49853/): Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ControlID iDSecure On-premises (critical 9.3)
- [CVE-2023-33369](https://insights.sbomify.com/CVE-2023-33369/): Path traversal in n/a (critical 9.1)
- [CVE-2025-49851](https://insights.sbomify.com/CVE-2025-49851/): Improper Authentication in ControlID iDSecure On-premises (high 8.7)
- [CVE-2025-49852](https://insights.sbomify.com/CVE-2025-49852/): Server-Side Request Forgery (SSRF) in ControlID iDSecure On-premises (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33371 is a critical vulnerability in n/a, published on 3 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33371 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-2023-33371/ (Markdown: https://insights.sbomify.com/CVE-2023-33371/index.md)
```

## Sources

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

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