CVE-2023-42017
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 Planning Analytics Local 2.0 could allow a remote attacker to upload arbitrary files, caused by the improper validation of file extensions. By sending a specially crafted HTTP request, a remote attacker could exploit this vulnerability to upload a malicious script, which could allow the attacker to execute arbitrary code on the vulnerable system. IBM X-Force ID: 265567.
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 Planning Analytics Local 2.0 contains an arbitrary file upload vulnerability stemming from improper validation of file extensions. Remote attackers can send specially crafted HTTP requests to upload malicious scripts (likely web shells) to the vulnerable system, achieving arbitrary code execution. The lack of proper file extension allowlisting and content validation enables this attack vector.
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.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Confirm IBM Planning Analytics Local installationLocate the IBM Planning Analytics Local installation directory on the system. Check for the presence of the tm1web or paw components which provide the web interface.Affected if IBM Planning Analytics Local 2.0 is installed and the web component is present
-
Verify the installed versionCheck the installed version of IBM Planning Analytics Local against the affected version 2.0. Use the IBM administration console or check version information in the installation directory.Affected if The installed version is exactly 2.0 (matches the affected version range)
-
Identify accessible file upload endpointsLocate the web application directories (such as the TM1Web or Planning Analytics Workspace web directories). Identify any endpoints or forms that accept file uploads.Affected if File upload functionality is enabled and accessible via the web interface
-
Inspect web-accessible directoriesExamine directories that are served by the web server for any uploaded script files (such as .jsp, .asp, .php, .exe files) that were not part of the original installation.Affected if Unexpected script or executable files are found in web-accessible directories
-
Review HTTP access logsAnalyze the web server access logs for the Planning Analytics application. Look for POST requests to upload endpoints that include unusual file extensions or multiple upload attempts.Affected if Logs show upload requests with suspicious file extensions or patterns indicating attempts to bypass extension validation
A system is affected if IBM Planning Analytics Local version 2.0 is installed with the web interface and file upload functionality enabled, and either suspicious files exist in web directories or unusual upload requests appear in logs.
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 file extension allowlisting with proper content-type validation, store uploads outside webroot, and apply IBM vendor patches when available. Until patched, disable or restrict file upload functionality if possible.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-42017 — 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-42017 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