CVE-2022-27548
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 user credentials in plain clear text which can be read by a local user.
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 stores user credentials in plaintext rather than using proper encryption or hashing. A local user with access to the system can read these unencrypted credentials, potentially gaining unauthorized access to user accounts or sensitive resources.
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.5.10= 7.1.2.6= 7.2.2.1CVSS 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.
-
Identify installed HCL Launch versionCheck the installed version of HCL Launch using the product's version command, about dialog, or installation directory metadata. Typical methods include running 'version' from the installation bin folder or inspecting the installation manifest.Affected if The installed version is 7.0.5.10, 7.1.2.6, or 7.2.2.1 (or falls within the range of affected versions)
-
Locate user credential storageIdentify where HCL Launch stores user credentials. This is typically in configuration files (such as conf/ldap.conf, conf/app.conf, or similar) or in the internal database if using an embedded database. Check the installation directory and data directory for files containing user authentication data.Affected if Credential storage files exist in the installation or data directories
-
Inspect credential storage formatOpen the identified credential storage file using a text editor or command-line tool (such as cat, grep, or less). Examine the format in which passwords or credentials are stored for user accounts.Affected if Credentials are stored in plaintext readable format rather than being hashed, encrypted, or obfuscated
A system is affected if it runs HCL Launch version 7.0.5.10, 7.1.2.6, or 7.2.2.1 AND stores user credentials in plaintext that can be read by a local user with file access.
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.
From vendor dataImplement proper credential encryption or hashing mechanisms for stored user credentials. Replace plaintext credential storage with secure storage methods such as encrypted configuration files, hashed passwords using strong algorithms (e.g., bcrypt, Argon2), or integration with a secure credential vault.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2022-27548 — 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-2022-27548 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