# CVE-2024-6912: Hardcoded MSSQL Credentials

> Hardcoded MSSQL credentials in PerkinElmer ProcessPlus allow attackers to remotely log in and access data on vulnerable installations.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jul 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-j7pf-cvcp-vq8q

## What is CVE-2024-6912?

CVE-2024-6912 is a critical vulnerability in PerkinElmer ProcessPlus, published on 22 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hard-coded MSSQL credentials in PerkinElmer ProcessPlus on Windows allows an attacker to login remove on all prone installations.This issue affects ProcessPlus: through 1.11.6507.0.

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

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

It affects 1 product.


Products: Perkinelmer Processplus.

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

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

## Is CVE-2024-6912 being exploited?

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

## Other vulnerabilities in PerkinElmer ProcessPlus

- [CVE-2024-6913](https://insights.sbomify.com/CVE-2024-6913/): Execution with Unnecessary Privileges (critical 9.3)
- [CVE-2024-6911](https://insights.sbomify.com/CVE-2024-6911/): Unauthenticated Local File Inclusion (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6912 is a critical vulnerability in PerkinElmer ProcessPlus, published on 22 Jul 2024. 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-2024-6912 exists.

Affected product: PerkinElmer ProcessPlus. 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-6912/ (Markdown: https://insights.sbomify.com/CVE-2024-6912/index.md)
```

## Sources

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

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