dbcve.org
Secure AccessApplication · Absolute

CVE-2024-37343

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-20
Fix available
A fix is available. Upgrade to 13.06 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
There is a cross-site scripting vulnerability in the Secure Access administrative console of Absolute Secure Access prior to version 13.06. Attackers with valid tunnel credentials can pass a limited-length script to the administrative console which is then temporarily stored where an administrator using a non-default configuration could click on it while the attacker has a valid tunnel session with the server. The scope is unchanged, there is no loss of confidentiality. Impact to system availability is none, impact to system integrity is high.

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 stored cross-site scripting (XSS) vulnerability exists in the Absolute Secure Access administrative console prior to version 13.06. Attackers with valid tunnel credentials can inject a limited-length script that gets temporarily stored and executes when an administrator with a non-default configuration clicks on it during an active tunnel session. The attack requires authenticated tunnel access and admin interaction to trigger.

MitigationUpgrade Absolute Secure Access to version 13.06 or later. Until patched, administrators should avoid clicking on untrusted or unexpected content in the administrative console during active tunnel sessions.

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
Secure AccessApplication
Affected:< 13.06

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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. Confirm Absolute Secure Access installation
    Locate the Absolute Secure Access client or server software on the system. Check installed programs or running services for 'Absolute Secure Access' or related process names.
    Affected if The software is present on the system
  2. Identify installed version
    Use system utilities to view the installed version of Absolute Secure Access (for example, check the application properties, installed programs list, or run 'ls -la' on the application directory if known). Compare the version number to 13.06.
    Affected if The installed version is lower than 13.06 (for example, 13.05, 13.04, or earlier)
  3. Verify administrative console accessibility
    Confirm the Absolute Secure Access administrative console web interface or management panel is accessible and active. This is typically accessed via a browser to the management IP/hostname.
    Affected if The administrative console is reachable and functional
  4. Check for active or possible tunnel sessions
    Determine whether tunnel functionality is enabled and can be activated. Review whether authenticated tunnel connections can be established by users with valid tunnel credentials.
    Affected if Tunnel sessions can be initiated and maintained by authenticated users

The environment is affected if Absolute Secure Access version is below 13.06 AND the administrative console is accessible while tunnel sessions are active, allowing an authenticated tunnel user to inject malicious scripts that execute when an administrator interacts with them during an active session.

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

Upgrade Absolute Secure Access to version 13.06 or later. Until patched, administrators should avoid clicking on untrusted or unexpected content in the administrative console during active tunnel sessions.

Recommended fix High confidence

version 13.06

  1. 1. Log into the Absolute Secure Access administrative console
  2. 2. Navigate to the system settings or version information section
  3. 3. Identify the current version (confirm it is below 13.06)
  4. 4. Obtain the Secure Access version 13.06 upgrade package from Absolute's official support portal or download center
  5. 5. Follow the vendor's documented upgrade procedure to apply version 13.06
  6. 6. After upgrade completion, verify the new version displays as 13.06
  7. 7. Confirm the XSS vulnerability is resolved by reviewing release notes or testing the affected vector

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

Fix this in Secure Access Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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