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

> Unauthenticated attackers can use default admin credentials to gain full control or cause denial of service in i-doit applications.

- **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:** 14 Sep 2023
- **Updated:** 26 Sep 2024
- **Also known as:** GHSA-xrrp-45rp-88qp

## What is CVE-2023-37755?

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

### Official description

i-doit pro 25 and below and I-doit open 25 and below are configured with insecure default administrator credentials, and there is no warning or prompt to ask users to change the default password and account name. Unauthenticated attackers can exploit this vulnerability to obtain Administrator privileges, resulting in them being able to perform arbitrary system operations or cause a Denial of Service (DoS).

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

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

It affects 1 product.


Products: I-Doit I-Doit.

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

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

## Is CVE-2023-37755 being exploited?

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

Public exploit code:

- https://github.com/leekenghwa/CVE-2023-37755---Hardcoded-Admin-Credential-in-i-doit-Pro-25-and-below (github_poc): https://github.com/leekenghwa/CVE-2023-37755---Hardcoded-Admin-Credential-in-i-doit-Pro-25-and-below

## Other vulnerabilities in n/a

- [CVE-2023-37756](https://insights.sbomify.com/CVE-2023-37756/): Weak cryptography in n/a (critical 9.8)
- [CVE-2019-1010248](https://insights.sbomify.com/CVE-2019-1010248/): SQL injection in I-doit (critical 9.8)
- [CVE-2019-25581](https://insights.sbomify.com/CVE-2019-25581/): i-doit CMDB 1.12 SQL Injection via objGroupID Parameter (high 8.8)
- [CVE-2024-8749](https://insights.sbomify.com/CVE-2024-8749/): SQL Injection vulnerability in Idoit pro (high 8.8)
- [CVE-2020-13826](https://insights.sbomify.com/CVE-2020-13826/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-37755 is a critical vulnerability in n/a, published on 14 Sep 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-37755 exists.

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-37755/ (Markdown: https://insights.sbomify.com/CVE-2023-37755/index.md)
```

## Sources

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

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