CVE-2024-37782
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 · uneditedAn LDAP injection vulnerability in the login page of Gladinet CentreStack v13.12.9934.54690 allows attackers to access sensitive data or execute arbitrary commands via a crafted payload injected into the username field.
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 · moderate confidenceLDAP injection vulnerability in Gladinet CentreStack v13.12.9934.54690 login page allows attackers to inject malicious LDAP statements into the username field, potentially bypassing authentication to access sensitive data or execute arbitrary commands. The critical CVSS score of 9.8 reflects the severe impact of successful exploitation on confidentiality, integrity, and availability.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm CentreStack versionLocate the installed version from the CentreStack admin interface (About page) or check the installation directory for version manifest files. Compare the version number to 13.12.9934.54690.Affected if The installed version is 13.12.9934.54690 or any earlier version of the v13.12.x line.
-
Verify LDAP integration is activeAccess the CentreStack admin panel and navigate to Settings > Directory Services or Authentication. Confirm that LDAP or Active Directory integration is enabled and configured.Affected if LDAP authentication is enabled and connected to an LDAP/Active Directory domain.
-
Confirm login page is network-accessibleDetermine if the CentreStack login page (typically at /login or the root URL of the server) is reachable from network segments outside your trusted internal network.Affected if The login page is exposed to untrusted or external networks.
-
Test username field for LDAP injectionOn the login page, attempt a login using special LDAP metacharacters in the username field such as: * ( ) \ or a null byte. Observe whether the application accepts the input without proper escaping or returns an LDAP error message.Affected if The application accepts special LDAP characters without rejecting the input or fails with an LDAP syntax error message.
You are affected if your CentreStack version is 13.12.9934.54690 or earlier, LDAP authentication is enabled, and the login page accepts unauthenticated LDAP query manipulation in the username field.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor-provided patch for CentreStack v13.12.9934.54690 and implement proper input validation with LDAP escaping for all user-supplied login credentials to prevent injection attacks.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37782 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37782 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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