dbcve.org
Identity ExposureApplication · Tenable

CVE-2024-1683

HIGH · 7.3 CVSS v3.1 Published 2024-02-23
Fix available
A fix is available. Upgrade to 3.59.4 or later.
See remediation →
75/100
Remediation priority · High
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
A DLL injection vulnerability exists where an authenticated, low-privileged local attacker could modify application files on the TIE Secure Relay host, which could allow for overriding of the configuration and running of new Secure Relay services.

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 confidence

A DLL injection vulnerability in TIE Secure Relay allows an authenticated low-privilege local attacker to modify application files, enabling configuration override and execution of arbitrary Secure Relay services through malicious DLL loading.

MitigationRestrict file system permissions on the TIE Secure Relay application directory to prevent low-privileged users from modifying application files and configurations; implement code signing and strict DLL search path controls.

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
Identity ExposureApplication
Affected:< 3.59.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
Low

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

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 if Tenable Identity Exposure is installed
    Check system for Tenable Identity Exposure (formerly Tenable.ad) installation by looking for its program directory or service
    Affected if Tenable Identity Exposure is not installed - not affected. If installed, continue to version check.
  2. Check the installed version of Tenable Identity Exposure
    Locate the Tenable Identity Exposure installation directory and check the version information, typically found in an About or Version file within the main program folder
    Affected if Version is 3.59.4 or higher - not affected. Version below 3.59.4 AND TIE Secure Relay is in use - potentially affected.
  3. Determine if TIE Secure Relay component is present
    Look for the TIE Secure Relay service or executable within the Tenable Identity Exposure installation directory
    Affected if TIE Secure Relay is not installed or not in use - not affected. If present, continue to permission check.
  4. Verify file system permissions on the application directory
    Examine NTFS permissions on the Tenable Identity Exposure installation directory to determine if low-privilege users (non-admin) have write or modify access to application files and configuration
    Affected if Standard users can modify application files or configurations - vulnerable condition present. Permissions properly restricted to administrators only - not vulnerable to this attack vector.
  5. Check for unexpected DLL files in the application directory
    Inspect the TIE Secure Relay bin or application directory for unrecognized or newly added DLL files that may indicate attempted injection
    Affected if Suspicious unrecognized DLL files present in the application directory - may indicate exploitation or attempted exploitation

A user is affected if they have Tenable Identity Exposure version below 3.59.4 with TIE Secure Relay installed AND low-privilege users have write access to application files or directories.

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

Restrict file system permissions on the TIE Secure Relay application directory to prevent low-privileged users from modifying application files and configurations; implement code signing and strict DLL search path controls.

Recommended fix High confidence

Identity Exposure 3.59.4 or later

  1. Upgrade Identity Exposure to version 3.59.4 or later

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

Fix this in Identity Exposure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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 locally
dbcve dependency scanner

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