CVE-2023-45703
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 may mishandle input validation of an uploaded archive file leading to a denial of service due to resource exhaustion.
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 contains a vulnerability in its archive file upload processing where input validation is not properly handled. An attacker can upload a specially crafted archive file that causes excessive resource consumption, leading to denial of service.
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.18>= 7.1.0.0, <= 7.1.2.14>= 7.2.0.0, <= 7.2.3.7>= 7.3.0.0, <= 7.3.2.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 HCL Launch versionLocate the installed HCL Launch version in the product UI under 'About' or check the installation directory for version manifest filesAffected if The installed version falls within 7.0.0.0-7.0.5.18, 7.1.0.0-7.1.2.14, 7.2.0.0-7.2.3.7, or 7.3.0.0-7.3.2.2
-
Verify archive upload feature statusCheck whether the component handling archive file uploads is enabled in the HCL Launch configuration or web UIAffected if Archive upload functionality is enabled and accessible to users
-
Inspect upload resource limitsReview HCL Launch server configuration files or admin settings for upload size limits, timeout values, and resource consumption controls on archive processingAffected if No resource limits are configured for archive file uploads or extraction operations
-
Check for input validation on uploadsExamine the upload processing configuration or logs to determine if file type validation, content inspection, or archive structure validation is performed before extractionAffected if No input validation or file type checking is performed on uploaded archive files
A user is affected if they run a vulnerable HCL Launch version within the affected ranges and have the archive upload feature enabled without resource limits or input validation configured.
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 strict input validation on uploaded archive files, including file type verification, size limits, and content inspection before processing. Consider implementing resource usage limits and timeouts for archive extraction operations.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45703 — 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-45703 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