CVE-2022-42447
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 Compass is vulnerable to Cross-Origin Resource Sharing (CORS). This vulnerability can allow an unprivileged remote attacker to trick a legitimate user into accessing a special resource and executing a malicious request.
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 Compass contains a CORS misconfiguration that allows unprivileged remote attackers to trick authenticated users into sending malicious cross-origin requests. The vulnerability permits unauthorized actions to be performed on behalf of legitimate users through specially crafted 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>= 2.0.0, <= 2.0.3>= 2.1.0, < 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 Compass versionLocate the Compass application installation directory and check the version file or product info. Common locations include the installation root or a version manifest. Alternatively, access the application's About or version information page if available through the web interface.Affected if The installed version falls within 2.0.0 to 2.0.3, or 2.1.0 to less than 2.2.1.
-
Locate CORS configuration filesSearch the Compass installation directory for configuration files that define CORS behavior. Look for files such as web.xml, server.xml, cors.xml, or any custom CORS filter configuration. These are typically found in the conf or config subdirectories of the application server.Affected if CORS configuration files exist and are accessible for review.
-
Inspect Access-Control-Allow-Origin header settingsOpen the identified CORS configuration file and examine the Access-Control-Allow-Origin setting. Look for how the allowed origins are defined and whether origin validation is implemented.Affected if The configuration allows a wildcard origin (*) or lacks proper origin validation for sensitive endpoints.
-
Check for origin validation logicIf a custom CORS filter is used, examine the filter code or configuration for the logic that validates the Origin header. Verify whether it validates against an explicit allowlist or performs proper validation before setting response headers.Affected if No strict origin validation exists, or the validation can be bypassed.
A user is affected if their installed HCL Compass version is within the vulnerable range AND the CORS configuration either uses a wildcard origin or lacks proper origin validation for sensitive endpoints.
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 · scoped2.2.1
Configure proper Access-Control-Allow-Origin header validation, avoid wildcard origins for sensitive endpoints, and implement strict CORS policies to validate allowed origins.
HCL Compass 2.2.1 or later
- Identify the current installed version of HCL Compass
- Backup the current installation and all associated data
- Download HCL Compass version 2.2.1 or later from the official HCL support portal
- Follow the HCL Compass upgrade documentation to install the new version
- Verify the upgrade was successful by logging into the application
- Confirm the CORS vulnerability is resolved by reviewing release notes or security advisories for the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-42447 — 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-42447 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