CVE-2023-43043
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 Application Suite - Maximo Mobile for EAM 8.10 and 8.11 could disclose sensitive information to a local user. IBM X-Force ID: 266875.
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 Mobile for EAM versions 8.10 and 8.11 contains an improper access control vulnerability that allows a local authenticated user to access sensitive information beyond their intended authorization level. The issue stems from insufficient authorization checks in the mobile application's data handling layer, potentially exposing confidential EAM data to unauthorized local users.
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= 8.10.0= 8.11.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify the installed Maximo Mobile versionCheck the application version through the Maximo Mobile administration console, or inspect the installed application manifest/package metadata. This is typically accessible via the About function in the mobile application or through the Maximo Asset Management backend system information.Affected if The installed version is 8.10.0 or 8.11.0 exactly.
-
Verify local user authentication configurationReview the Maximo Mobile authentication settings to confirm whether local user accounts (as opposed to centralized directory users) are enabled for mobile access. Check the user administration interface in Maximo and the mobile-specific security configuration.Affected if Local user authentication is enabled and users exist with direct local Maximo credentials.
-
Examine role-based access control (RBAC) assignmentsReview the role assignments for mobile-accessible users in Maximo. Inspect which security groups and roles are mapped to mobile users and whether users have been assigned to roles beyond their job function.Affected if Users have been granted roles that provide access to EAM data beyond their organizational need, or role inheritance creates unintended data access paths.
-
Inspect data access path configurationsExamine the mobile application's data synchronization settings and data filter definitions. Check which EAM data objects (work orders, assets, inventory) are configured for mobile access and whether these filters are properly scoped to user authorization levels.Affected if Data filters are either not defined or allow broader data visibility than the user's assigned security groups should permit.
A user is affected if they have IBM Maximo Mobile for EAM version 8.10.0 or 8.11.0 installed AND local user authentication is enabled with insufficiently scoped role-based access controls.
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 the IBM fix pack for this vulnerability (contact IBM for specific patch version). Verify that role-based access controls are properly enforced for all data access paths in Maximo Mobile, and restrict local system access to authorized personnel only.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43043 — 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-43043 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