CVE-2023-47161
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 · uneditedIBM UrbanCode Deploy (UCD) 7.1 through 7.1.2.14, 7.2 through 7.2.3.7, and 7.3 through 7.3.2.2 may mishandle input validation of an uploaded archive file leading to a denial of service due to resource exhaustion. IBM X-Force ID: 270799.
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 confidenceIBM UrbanCode Deploy mishandles input validation for uploaded archive files. When users upload archive files (component templates, applications, or plugins), the system fails to properly validate archive contents/size before processing, allowing specially crafted archives to exhaust server resources (memory, disk, or CPU) and cause 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 the installed IBM UrbanCode Deploy versionLocate the version information through the product's management console, installation logs, or version file in the installation directoryAffected if The installed version falls within the affected ranges: 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
-
Determine if the system has exposed upload endpointsCheck network configuration or access controls to see if component template, application, or plugin upload interfaces are accessible to users or external systemsAffected if Upload endpoints for archives are exposed without additional access restrictions beyond standard authentication
-
Verify whether archive uploads are permitted in the deployment configurationReview the server configuration or security settings that control whether users can upload component templates, applications, or plugins as archive filesAffected if Users with standard permissions can upload archive files to the system
-
Inspect existing resource limits for archive processingExamine server configuration files or management settings for any configured limits on archive file size, extraction depth, compression ratios, or memory/disk quotas during upload processingAffected if No explicit resource limits (file size, extraction quota, or compression ratio limits) are configured for archive uploads
-
Check for anomalous archive upload activityReview server logs or monitoring data for any unusual patterns in archive upload requests, such as unusually large files, excessive nested archives, or high-frequency upload attemptsAffected if Monitoring reveals archive uploads that could indicate resource exhaustion attempts or the system lacks such monitoring capabilities
A system is affected if it runs a version of IBM UrbanCode Deploy within the listed affected ranges AND allows users to upload archive files without proper resource limits 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 dataUpgrade to a patched version if available. Implement aggressive input validation including file size limits, archive compression ratio limits, nested archive depth limits, and extraction quota controls on the upload endpoint. Consider implementing upload rate limiting and monitoring for anomalous file upload patterns.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-47161 — 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-47161 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