dbcve.org
Huntflow EnterpriseApplication · Huntflow

CVE-2021-37935

HIGH · 7.5 CVSS v3.1 Published 2021-12-10
Fix available
A fix is available. Upgrade to after 3.10.4 or later.
See remediation →
84/100
Remediation priority · High
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
An information disclosure vulnerability in the login page of Huntflow Enterprise before 3.10.4 could allow an unauthenticated, remote user to get information about the domain name of the configured LDAP server. An attacker could exploit this vulnerability by requesting the login page and searching for the "isLdap" JavaScript parameter in the HTML source code.

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 login page of Huntflow Enterprise before version 3.10.4 exposes the configured LDAP server's domain name in an unencrypted JavaScript parameter named 'isLdap' within the HTML source code. An unauthenticated remote attacker can discover this sensitive LDAP configuration by simply requesting the login page and inspecting the page source.

MitigationUpgrade to Huntflow Enterprise version 3.10.4 or later to remove the LDAP domain disclosure from the login page. Additionally, ensure sensitive LDAP configuration is not exposed in client-side code.

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
Huntflow EnterpriseApplication
Affected:<= 3.10.4

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
None
Availability
None

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

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. Locate the Huntflow Enterprise login page
    Identify the URL where the Huntflow login page is hosted in your environment (typically at /login or /auth/login path on the Huntflow server).
    Affected if The login page is publicly accessible without authentication.
  2. Determine the installed Huntflow version
    Check your installed Huntflow Enterprise version number. This may be visible in the application UI footer, in the /about endpoint, or through administrative panels. Compare it against the affected range: versions <= 3.10.4 are vulnerable.
    Affected if Your installed version is 3.10.4 or lower.
  3. Inspect login page HTML source for isLdap parameter
    Request the login page using a browser or curl, then view the page source (in browsers: right-click > View Page Source). Search for the JavaScript string 'isLdap' within the HTML source code.
    Affected if The 'isLdap' parameter is present in the page source.
  4. Verify LDAP domain disclosure
    If 'isLdap' is found, examine its value. The vulnerable version exposes the configured LDAP server's domain name in plain text within this JavaScript parameter.
    Affected if The 'isLdap' parameter contains a domain name or LDAP configuration detail (such as 'isLdap: "domain.example.com"' or similar LDAP-related string).

Your environment is affected if you are running Huntflow Enterprise version 3.10.4 or lower AND the login page HTML source contains an 'isLdap' JavaScript parameter exposing LDAP domain configuration.

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 a release after 3.10.4
Interim mitigation

Upgrade to Huntflow Enterprise version 3.10.4 or later to remove the LDAP domain disclosure from the login page. Additionally, ensure sensitive LDAP configuration is not exposed in client-side code.

Recommended fix High confidence

Huntflow Enterprise 3.10.4 or later

  1. 1. Backup your current Huntflow Enterprise installation and database
  2. 2. Upgrade Huntflow Enterprise to version 3.10.4 or later
  3. 3. Verify the upgrade was successful by checking the version number
  4. 4. Test the login page by viewing the HTML source code to confirm the 'isLdap' JavaScript parameter no longer exposes LDAP domain information

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

Fix this in Huntflow Enterprise Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-37935 — 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-2021-37935 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