CVE-2023-45702
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 · uneditedAn HCL UrbanCode Deploy Agent installed as a Windows service in a non-standard location could be subject to a denial of service attack by local accounts..
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 confidenceWhen HCL UrbanCode Deploy Agent is installed as a Windows service in a non-standard (non-default) installation directory, local authenticated users can exploit improper service binary or configuration handling to cause a denial of service, likely by tampering with service files or executing malicious binaries from the non-standard path.
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.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 if HCL Launch is installedCheck the Windows system for HCL Launch (UrbanCode Deploy) Agent installation. Look for service entries named 'HCL UrbanCode Deploy Agent' or 'ucd' in Windows services. Use PowerShell: Get-Service | Where-Object {$_.DisplayName -like '*UrbanCode*' -or $_.DisplayName -like '*HCL*' -or $_.Name -like '*ucd*'}Affected if No HCL Launch service is found, meaning the product is not installed and is not affected.
-
Determine the installation directoryFind the executable path of the HCL service. Use PowerShell: Get-WmiObject Win32_Service | Where-Object {$_.DisplayName -like '*UrbanCode*' -or $_.DisplayName -like '*HCL*'} | Select-Object Name, DisplayName, PathName. Extract the directory from the PathName value.Affected if The installation path is in a non-standard directory (not the default installation location). This condition must be true for the vulnerability to apply.
-
Check installed version against affected rangesLocate the version file or check the installed version. Common locations include the installation directory or registry. Use the PathName from the previous step to navigate to the installation folder and look for a version file, or run: (Get-Item 'C:\Program Files\HCL\UCD\version.xml').Version - adjusting the path to match your actual installation directory.Affected if The installed version falls within >= 7.2.0.0 AND <= 7.2.3.7, OR >= 7.3.0.0 AND <= 7.3.2.2. Versions outside these ranges are not affected.
-
Verify filesystem permissions on the service directoryReview the permissions on the installation directory identified in step 2. Use PowerShell: Get-Acl -Path 'INSTALLATION_PATH' | Select-Object Owner, AccessToString. Check if standard users or low-privileged accounts have write or modify permissions.Affected if The service directory has weak or overly permissive access controls allowing unauthorized local users to modify service files or configurations.
A user is affected if HCL Launch is installed as a Windows service in a non-standard directory, the version falls within the affected ranges (7.2.0.0-7.2.3.7 or 7.3.0.0-7.3.2.2), and the service directory has weak filesystem permissions.
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 · scopedInstall the HCL UrbanCode Deploy Agent in the default/standard installation location, or if a non-standard path is required, ensure strict filesystem permissions on the service directory to prevent unauthorized local access.
HCL Launch 7.3.3.0 or later (or 7.2.4.0 or later for the 7.2.x release line)
- 1. Identify the current HCL Launch version by checking the installed agent version or the version listed in the HCL Launch server UI
- 2. Navigate to HCL Official Support Portal (support.hcltechsw.com) and locate the downloads section for HCL Launch
- 3. Download HCL Launch version 7.3.3.0 or later (or 7.2.4.0 or later for the 7.2.x track)
- 4. Follow HCL's standard upgrade procedure for the UrbanCode Deploy Agent - this typically involves: stopping the agent service, backing up the agent installation directory, installing the new version, and restarting the service
- 5. If the agent was installed in a non-standard location on Windows, ensure the new installation uses proper Windows service permissions and directory locations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-45702 — 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-45702 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