CVE-2024-45077
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 Maximo Asset Management 7.6.1.3 MXAPIASSET API is vulnerable to unrestricted file upload which allows authenticated low privileged user to upload restricted file types with a simple method of adding a dot to the end of the file name if Maximo is installed on Windows operating system.
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 Maximo Asset Management 7.6.1.3 MXAPIASSET API allows authenticated low-privileged users to bypass file type restrictions by appending a dot to filenames, enabling upload of restricted file types. This unrestricted file upload vulnerability only affects Windows installations.
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.6.1.3CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Verify IBM Maximo Asset Management versionCheck the installed Maximo Asset Management version in your environment. This is typically visible in the Maximo Application Suite admin console, or by querying the maxversion table in the database, or checking the installation logs.Affected if The installed version is 7.6.1.3 exactly. If running a different version, this specific CVE does not apply.
-
Confirm Windows installation platformIdentify the operating system hosting the Maximo application server. This can be checked via systeminfo (Windows), the server properties in Maximo admin console, or by checking the OS where the Maximo binaries are installed.Affected if The Maximo application server runs on Windows. This vulnerability only affects Windows installations; Linux and other platforms are not impacted.
-
Verify MXAPIASSET API availabilityCheck whether the MXAPIASSET API endpoint is enabled and accessible in your Maximo environment. This API is typically exposed via REST services. Check the Maximo integration framework configuration or REST API deployment settings.Affected if The MXAPIASSET API is enabled and exposed. The vulnerability exists specifically within this API endpoint.
-
Identify low-privileged user upload permissionsReview user group permissions in Maximo, specifically checking if authenticated users with low-privilege roles (non-admin) have file upload capabilities through the MXAPIASSET API. Check group membership and permission settings in Maximo Security or the Maximo Administration application.Affected if Low-privileged (non-administrator) authenticated users have file upload permissions via the MXAPIASSET API.
-
Test file upload bypass possibilityIf you have access to a low-privileged test account, attempt to upload a file with a restricted extension (e.g., .exe, .js) appended with a trailing dot (e.g., maliciousfile.exe.) through the MXAPIASSET API endpoint to see if the restriction is bypassed.Affected if The upload succeeds with a trailing dot bypass, confirming the vulnerability is present.
Your environment is affected if you run IBM Maximo Asset Management 7.6.1.3 on Windows with the MXAPIASSET API enabled and low-privileged users having file upload 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.
From vendor dataImplement server-side file type validation that cannot be bypassed by filename manipulation (e.g., adding trailing dots), restrict file upload permissions for low-privileged users, and apply IBM security patches when available.
- Consultation3.0 h
- Implementation8.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45077 — 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-2024-45077 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