CVE-2023-37517
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 · uneditedMissing "no cache" headers in HCL Leap permits sensitive data to be cached.
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 confidenceHCL Leap fails to set cache-control headers on responses containing sensitive data, allowing browsers to locally cache this information. Attackers with local access or shared workstations could retrieve cached sensitive data from the browser history or cache files.
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>= 1.1, < 1.1.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed HCL Leap versionLocate the version information in the Domino Leap installation directory, typically in a version file or via the Leap administration interface under System > Information > VersionAffected if The installed version is 1.1.0 or 1.1.1 (versions >= 1.1.0 and < 1.1.2 are affected)
-
Confirm Leap deployment is accessibleAccess the HCL Leap web application URL and verify it is operationalAffected if The application is running and accessible to users
-
Inspect HTTP response headers for sensitive endpointsUse browser developer tools (Network tab) or a command-line tool like curl to capture HTTP response headers from pages that contain or process sensitive user data (e.g., forms with personal information, admin pages)Affected if Responses lack cache-control: no-store, cache-control: no-cache, and Pragma: no-cache headers
-
Examine browser cache for Leap contentCheck the browser cache directory or use browser developer tools to see if Leap pages containing sensitive data are being stored locallyAffected if Sensitive form data or user information is found in the browser cache
You are affected if the installed Leap version is 1.1.0 or 1.1.1 and the HTTP responses lack cache-control headers, allowing sensitive data to be stored in the browser cache.
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 · scoped1.1.2
Configure HCL Leap to include appropriate cache-control headers (no-store, no-cache, must-revalidate) and Pragma: no-cache headers on all responses containing sensitive data to prevent browser caching.
HCL Domino Leap 1.1.2
- Back up the current HCL Domino Leap installation and all application data
- Download HCL Domino Leap version 1.1.2 from the official HCL support portal (support.hcl-software.com)
- Follow HCL's standard upgrade procedure for Domino Leap, stopping the Domino Leap server before the upgrade
- Install HCL Domino Leap 1.1.2 using the HCL installation wizard or command-line tools
- Start the Domino Leap server after installation completes
- Verify the version shows 1.1.2 in the Domino Leap admin console
- Test that applications function correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37517 — 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-2023-37517 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