dbcve.org
InvestigateApplication · Siren

CVE-2021-36794

CRITICAL · 9.8 CVSS v3.1 Published 2021-11-02
Fix available
A fix is available. Upgrade to 11.1.4 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
In Siren Investigate before 11.1.4, when enabling the cluster feature of the Siren Alert application, TLS verifications are disabled globally in the Siren Investigate main process.

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

When the cluster feature in Siren Alert is enabled on Siren Investigate versions before 11.1.4, the application globally disables TLS certificate verification in the main process. This removes SSL/TLS validation for all connections system-wide, enabling man-in-the-middle attacks and unauthorized data interception.

MitigationUpgrade Siren Investigate to version 11.1.4 or later, which fixes the TLS verification bypass in the cluster feature.

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
InvestigateApplication
Affected:< 11.1.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
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 Siren Investigate version
    Locate and retrieve the installed version of Siren Investigate in your environment
    Affected if Version is below 11.1.4
  2. Compare version to affected range
    Verify the installed version against the affected range: versions < 11.1.4 are vulnerable
    Affected if Installed version is less than 11.1.4
  3. Determine if cluster feature is active
    Inspect the Siren Investigate configuration to check whether the cluster feature is enabled
    Affected if Cluster feature is enabled and version is below 11.1.4

You are affected if Siren Investigate version is below 11.1.4 AND the cluster feature is enabled, as this combination results in global TLS certificate verification being disabled.

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 11.1.4 or later
Fixed in 11.1.4
Interim mitigation

Upgrade Siren Investigate to version 11.1.4 or later, which fixes the TLS verification bypass in the cluster feature.

Recommended fix High confidence

11.1.4

  1. Backup the Siren Investigate configuration and data directory before upgrading
  2. Stop the Siren Investigate service
  3. Upgrade Siren Investigate to version 11.1.4 or later
  4. Verify the upgrade was successful by checking the version number in the UI or via API
  5. Restart the Siren Investigate service
  6. Confirm TLS verification is now properly enforced after upgrading

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

Fix this in Investigate Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,220
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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