CVE-2023-0587
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 · uneditedA file upload vulnerability in exists in Trend Micro Apex One server build 11110. Using a malformed Content-Length header in an HTTP PUT message sent to URL /officescan/console/html/cgi/fcgiOfcDDA.exe, an unauthenticated remote attacker can upload arbitrary files to the SampleSubmission directory (i.e., \PCCSRV\TEMP\SampleSubmission) on the server. The attacker can upload a large number of large files to fill up the file system on which the Apex One server is installed.
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 confidenceUnauthenticated file upload vulnerability in Trend Micro Apex One server (build 11110) allows remote attackers to send malformed HTTP PUT requests with manipulated Content-Length headers to /officescan/console/html/cgi/fcgiOfcDDA.exe, bypassing authentication and uploading arbitrary files to the SampleSubmission directory. This enables complete disk space exhaustion for 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 dataall versionsCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 if Apex One server is installedCheck for Trend Micro Apex One installation directories or services on the system. Look for directories containing 'Apex One', 'officescan', or related paths in Program Files or system directories.Affected if Apex One server software is found on the system
-
Determine the installed Apex One build versionLocate version or build information in the Apex One installation directory, typically in a version.txt, readme, or within the main application executable properties. Compare the build number to 11110.Affected if The installed build version is 11110 or falls within the affected version range
-
Verify the affected CGI endpoint is accessibleAttempt to access the URI /officescan/console/html/cgi/fcgiOfcDDA.exe via HTTP or HTTPS on the Apex One management port (default 4343). Check if the endpoint responds or exists.Affected if The fcgiOfcDDA.exe endpoint is reachable and responds to requests
-
Inspect the SampleSubmission directory for unexpected filesLocate the SampleSubmission directory within the Apex One installation path or web root. List all files and check for unauthorized or unexpected uploads that were not submitted through legitimate means.Affected if The SampleSubmission directory contains files that were not intentionally uploaded or contains an unusually high number of files
-
Review HTTP access logs for suspicious PUT requestsExamine web server access logs (IIS, Apache, or built-in web server logs) for PUT requests to /officescan/console/html/cgi/fcgiOfcDDA.exe, especially those with manipulated or mismatched Content-Length headers.Affected if Logs show unauthenticated PUT requests to the affected endpoint or requests with abnormal Content-Length values
Apex One server is affected if it is installed, runs build 11110 or an affected version, and the vulnerable fcgiOfcDDA.exe endpoint is accessible without authentication.
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 dataApply vendor-supplied patch for Apex One build 11110; restrict network access to management interfaces; monitor SampleSubmission directory for unauthorized files.
- Consultation3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0587 — 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-0587 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