CVE-2024-42196
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 · uneditedHCL Launch stores potentially sensitive information in log files that could be read by a local user with access to HTTP request logs.
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 confidenceHCL Launch (deployment automation software) logs HTTP request data to files that may contain sensitive information such as credentials, tokens, or PII. A local user with access to these log files can read the sensitive data.
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>= 7.0.0.0, < 7.0.5.25>= 7.1.0.0, < 7.1.2.21>= 7.2.0.0, < 7.2.3.14CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Determine HCL Launch installed versionLocate the HCL Launch installation directory and find the version information file or use the product's version command. Common locations include a version.txt file, about page in the web UI, or the initiarray/version property in installation files.Affected if The installed version falls within one of these ranges: >= 7.0.0.0 and < 7.0.5.25, OR >= 7.1.0.0 and < 7.1.2.21, OR >= 7.2.0.0 and < 7.2.3.14
-
Locate HTTP request log filesIdentify the directory where HCL Launch stores its log files, typically under the installation directory in a logs or var/log folder. Look for log files that capture HTTP request data such as access logs, http logs, or request logs.Affected if HTTP request log files exist in the installation and the version is within the affected ranges
-
Verify if request logging includes sensitive dataExamine the log configuration files (such as log4j or logging config files) to determine if HTTP request bodies, headers, or query parameters are being logged. Check whether any redaction or masking of sensitive fields (passwords, tokens, authorization headers) is configured.Affected if Request logging is enabled and captures full request bodies or headers without redaction, and the version is affected
-
Check log file permissionsReview file system permissions on the identified log directory and log files. Determine what users or groups have read access to these files.Affected if Log files are readable by non-administrator users or users outside the authorized administrator group
You are affected if HCL Launch version is in the vulnerable ranges AND HTTP request logging is enabled without redaction AND log files are accessible to unauthorized local users.
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 · scoped7.0.5.257.1.2.217.2.3.14
Configure HCL Launch to redact or mask sensitive fields in HTTP request logs, and ensure log file permissions restrict access to authorized administrators only.
7.0.5.25 (for 7.0.x), 7.1.2.21 (for 7.1.x), or 7.2.3.14 (for 7.2.x)
- 1. Identify the currently installed HCL Launch version using the UI (Help > About) or CLI (./launch -v)
- 2. Based on the current version line, plan upgrade to the minimum fixed version: 7.0.5.25 for 7.0.x, 7.1.2.21 for 7.1.x, or 7.2.3.14 for 7.2.x
- 3. Review HCL Launch upgrade documentation at support.hcl-software.com for your version line
- 4. Perform a full backup of the HCL Launch server including the conf, var, and plugins directories
- 5. Stop the HCL Launch server before upgrading
- 6. Download the appropriate fixed version installer from HCL Flexnet/Support Portal
- 7. Run the upgrade installer following HCL's standard upgrade procedure
- 8. After upgrade, verify the version matches the target fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-42196 — 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-42196 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