CVE-2024-37345
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 · uneditedThere is a cross-site scripting vulnerability in the Secure Access administrative UI of Absolute Secure Access prior to version 13.06. Attackers can pass a limited-length script to the administrative UI which is then stored where an administrator can access it. 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 · high confidenceThis is a stored cross-site scripting (XSS) vulnerability in the administrative UI of Absolute Secure Access client software. Attackers can inject malicious scripts with limited length that get persisted in the administrative interface and execute when an administrator views the affected content, leading to potential integrity compromise.
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< 13.06CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Absolute Secure Access versionCheck the installed version of Absolute Secure Access client software on the system. This is typically found in the application properties, about dialog, or installed programs list depending on the OS. Use system inventory tools or check the application's built-in version information.Affected if The installed version is lower than 13.06 (for example, 13.05, 13.04, earlier versions)
-
Confirm administrative UI is in useVerify that the Absolute Secure Access client is configured with administrative or management interface access. This vulnerability specifically affects the administrative UI component.Affected if Administrative UI is enabled and accessible on the affected installation
-
Review admin interface input fieldsExamine the administrative UI for input fields that accept user-supplied data and persist it. Look for fields in configuration panels, client settings, or policy definitions where data may be stored.Affected if The admin UI contains input fields that accept and store user-supplied content without visible sanitization indicators
An installation is affected if the Absolute Secure Access client version is below 13.06 and the administrative UI is accessible and accepts user-supplied input.
Generated from the published advisory. Verify against your own configuration.
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 · scoped13.06
Upgrade Absolute Secure Access to version 13.06 or later to obtain the patched version that properly sanitizes input in the administrative UI.
13.06
- 1. Verify current installation version by accessing the Secure Access administrative UI and navigating to the system information or about section
- 2. Create a full backup of the current configuration following vendor documentation
- 3. Download Absolute Secure Access version 13.06 or later from the official Absolute download portal at www.absolute.com
- 4. Review the upgrade instructions in the Absolute Secure Access administration guide
- 5. Apply the upgrade through the administrative interface or CLI as documented by Absolute
- 6. After upgrade completes, verify the new version is 13.06 or later
- 7. Log in to the administrative UI and confirm the XSS fix is applied by checking that the vulnerable input fields properly sanitize script content
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-37345 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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