dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2024-36426

HIGH · 7.5 CVSS v3.1 Published 2024-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
In TARGIT Decision Suite 23.2.15007.0 before Autumn 2023, the session token is part of the URL and may be sent in a cleartext HTTP session.

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

TARGIT Decision Suite embeds session tokens in URLs, which can be logged in server/proxy logs, browser history, or transmitted in cleartext when HTTP is used. This allows attackers to hijack user sessions by obtaining the exposed token.

MitigationEnforce HTTPS exclusively to prevent cleartext transmission, and migrate session management from URL-based tokens to HTTP-only cookies or proper authorization headers.

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
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. Identify TARGIT Decision Suite installation and version
    Check for TARGIT installation directories, registry entries, or running services. Common paths include C:\Program Files\TARGIT or installation directories configured during setup. Look for executables like TARGITServer.exe or related services.
    Affected if TARGIT Decision Suite is installed and the version cannot be confirmed as patched, or the version is unknown
  2. Verify session token handling in URLs
    Analyze HTTP traffic or application logs to observe whether session identifiers, tokens, or authentication credentials appear as URL parameters (e.g., ?sessionid=XYZ or ?token=ABC) rather than in HTTP headers or cookies.
    Affected if Session tokens are transmitted as URL query parameters or path segments rather than in secure HTTP-only cookies or authorization headers
  3. Confirm HTTP vs HTTPS configuration
    Inspect the TARGIT web server configuration or proxy settings to determine whether HTTP, HTTPS, or both are enabled. Check for redirect rules or HSTS settings that enforce encrypted connections.
    Affected if HTTP is enabled or HTTPS is not enforced, allowing session tokens to be transmitted in cleartext
  4. Examine server and proxy logs for token exposure
    Review web server access logs, proxy logs, or application logs for entries containing session token values in the requested URLs. Search for patterns like 'sessionid', 'token', 'sid' in URL paths or query strings.
    Affected if Logs contain URLs with visible session tokens, indicating past exposure in logged data

A user is affected if TARGIT Decision Suite is running and session tokens are embedded in URLs rather than being managed through secure, HTTP-only mechanisms, especially if HTTP access is permitted.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enforce HTTPS exclusively to prevent cleartext transmission, and migrate session management from URL-based tokens to HTTP-only cookies or proper authorization headers.

Recommended fix Moderate confidence

TARGIT Decision Suite Autumn 2023 or later (any version after the vulnerable 23.2.15007.0 release)

  1. Upgrade TARGIT Decision Suite to Autumn 2023 release or later, which contains the fix for this vulnerability.
  2. Ensure the TARGIT server is configured to enforce HTTPS connections to prevent cleartext transmission of session tokens.
  3. After upgrading, verify that session tokens are no longer exposed in URLs and are transmitted only over encrypted HTTPS connections.
  4. Review server configuration to confirm HTTP to HTTPS redirection is enabled.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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