IBM Maximo Asset Management 7.6 could allow a physical user of the system to obtain sensitive information from a previous user of the same m
IBM Maximo Asset Management 7.6 could allow a physical user of the system to obtain sensitive information from a previous user of the same machine. IBM X-Force ID: 156311.
- Published
- Jun 5, 2019
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 21th percentile
- CWE
- CWE-269
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
8
Monitor
Low priority for now.
- CVSS
- 8 / 40 · 2.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- 2.1
- CNA · ibm
- 2.1
- agree
CVSS:3.0/C:L/S:U/UI:N/A:N/I:N/PR:L/AV:P/AC:L/RL:O/E:U/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | control desk | cpe:2.3:a:ibm:control_desk |
| ibm | maximo asset management | cpe:2.3:a:ibm:maximo_asset_management |
| ibm | maximo for aviation | cpe:2.3:a:ibm:maximo_for_aviation |
| ibm | maximo for life sciences | cpe:2.3:a:ibm:maximo_for_life_sciences |
| ibm | maximo for nuclear power | cpe:2.3:a:ibm:maximo_for_nuclear_power |
| ibm | maximo for oil and gas | cpe:2.3:a:ibm:maximo_for_oil_and_gas |
| ibm | maximo for transportation | cpe:2.3:a:ibm:maximo_for_transportation |
| ibm | maximo for utilities | cpe:2.3:a:ibm:maximo_for_utilities |
| ibm | smartcloud control desk | cpe:2.3:a:ibm:smartcloud_control_desk |
| ibm | tivoli integration composer | cpe:2.3:a:ibm:tivoli_integration_composer |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm control desk7.6.0
- ibm control desk7.6.0.1
- ibm control desk7.6.1
- ibm maximo asset management7.6
- ibm maximo for aviation7.6
- ibm maximo for aviation7.6.1
- ibm maximo for aviation7.6.2
- ibm maximo for aviation7.6.2.1
- ibm maximo for aviation7.6.3
- ibm maximo for life sciences7.6
- ibm maximo for nuclear power7.6.0
- ibm maximo for oil and gas7.6.0
- ibm maximo for transportation7.6.1
- ibm maximo for transportation7.6.2
- ibm maximo for transportation7.6.2.1
- ibm maximo for transportation7.6.2.2
- ibm maximo for transportation7.6.2.3
- ibm maximo for transportation7.6.2.4
- ibm maximo for utilities7.6
- ibm smartcloud control deskall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (ibm). Independent of NVD's CPE analysis and usually ahead of it.
IBM Maximo Asset Management
- 7.6affected
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-4409IBM Maximo Asset Management 7.6.0 and 7.6.1 could allow a remote attacker to conduct phishing attacks, using a tabnabbing attack.32Monitor
- CVE-2018-2028IBM Maximo Asset Management 7.6 could allow a an authenticated user to replace a target page with a phishing site which could allow the atta26Monitor
- CVE-2019-4644IBM Maximo Asset Management 7.6 is vulnerable to cross-site scripting.24Monitor
- CVE-2022-22330IBM Control Desk 7.6.1 could allow a remote attacker to obtain sensitive information, caused by the failure to set the HTTPOnly flag.21Monitor
- CVE-2021-20559IBM Control Desk 7.6.1.2 and 7.6.1.3 is vulnerable to cross-site scripting.21Monitor
- CVE-2019-4749IBM Maximo Asset Management 7.6 is vulnerable to cross-site scripting.21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Physical access to the device is required.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-269 · Improper Privilege ManagementCVSS vector
CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Root cause
To simplify setup, a service account is granted broad, cluster-wide permissions. The principle of least privilege is skipped during installation.
The bug in code
The whole CWE-269 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
kind: ClusterRolerules: - apiGroups: ["*"] resources: ["*"] verbs: ["*"]Fixed
kind: Rolemetadata: namespace: lodos-systemrules: - apiGroups: ["apps"] resources: ["deployments"] verbs: ["get", "list", "update"]Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.