dbcve.org
GabinetApplication · Dreryk

CVE-2024-3699

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 9.17.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Use of hard-coded password to the patients' database allows an attacker to retrieve sensitive data stored in the database. The password is the same among all drEryk Gabinet installations.This issue affects drEryk Gabinet software versions from 7.0.0.0 through 9.17.0.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The drEryk Gabinet medical software versions 7.0.0.0 through 9.17.0.0 contain a hard-coded password embedded in the application code that provides direct access to the patient database. Since this identical password is used across all installations, any attacker who obtains or guesses this password can access sensitive patient health records and personal identifiable information (PII) stored in the database.

MitigationReplace the hardcoded password with a secure credential management system (e.g., environment variables, secrets manager, or encrypted configuration) and force password rotation on all existing installations. Consider auditing database access logs for unauthorized access since the vulnerability has been publicly disclosed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GabinetApplication
Affected:>= 7.0.0.0, < 9.17.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Dreryk Gabinet version
    Check the application version through the software's About section, installation directory metadata, or Windows Programs and Features. Compare the version number to the affected range: 7.0.0.0 through 9.17.0.0.
    Affected if The installed version falls within the range >= 7.0.0.0 and < 9.17.0.0
  2. Locate application executable and configuration files
    Search the Dreryk Gabinet installation directory for executable files (.exe), configuration files (.config, .xml, .ini), and any embedded resources. Common locations include C:\Program Files\Dreryk\Gabinet or the application's default installation path.
    Affected if Application files are found in the installation directory
  3. Inspect application binaries for hardcoded credentials
    Search within the application executable files, DLLs, or configuration files for hardcoded password strings. Use a text search or hex editor to look for database connection strings containing password fields.
    Affected if A hardcoded password is found embedded in the application code or configuration files
  4. Verify database connection uses hardcoded credential
    Attempt to connect to the patient database using the discovered hardcoded password from the application code. Check if the database accepts this credential for authentication.
    Affected if The database accepts authentication using the hardcoded password found in the application
  5. Review database access controls
    Examine the database user accounts and authentication method configured for the Dreryk Gabinet application. Determine if the application uses a shared credential across installations.
    Affected if The database is configured with a hardcoded credential shared across installations rather than unique per-installation credentials

You are affected if Dreryk Gabinet version 7.0.0.0 through 9.17.0.0 is installed AND the application contains a hardcoded password that provides direct database access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 9.17.0.0 or later
Fixed in 9.17.0.0
Interim mitigation

Replace the hardcoded password with a secure credential management system (e.g., environment variables, secrets manager, or encrypted configuration) and force password rotation on all existing installations. Consider auditing database access logs for unauthorized access since the vulnerability has been publicly disclosed.

Recommended fix High confidence

9.17.0.0

  1. 1. Backup the current Gabinet installation and database.
  2. 2. Download the fixed version (9.17.0.0) from the official vendor source.
  3. 3. Stop the Gabinet service.
  4. 4. Upgrade the Gabinet installation to version 9.17.0.0.
  5. 5. Start the Gabinet service.
  6. 6. Verify the application functions correctly and the hard-coded password has been removed or changed.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gabinet Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3699 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data