CVE-2005-1601: MRO Maximo Self Service 4 and 5 stores certain information under the web document root using file extensions t

Routine

MEDIUM 5.0DOWNGRADE

CVE-2005-1601 is a medium-severity flaw (CVSS 5.0) affecting maximo self service. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

MRO Maximo Self Service 4 and 5 stores certain information under the web document root using file extensions that are not processed by Tomcat, which allows remote attackers to obtain sensitive information via a direct request for the file, such as MXServer.properties.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.0 (Medium)
EPSS exploit chance	1.4% (top 28%)
CISA exploited list	No
Published	2005-05-16
Last modified	2026-06-16

Publisher (CNA): MITRE · Vendor: mro software

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2005-05-16 04:00 UTCPublished CVE record published
2026-06-16 22:13 UTCUpdated Record last modified

mro software maximo self service DOWNGRADE

Affected: 4.0 · 5.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 4.0

1. Check installed version

apt-cache policy maximo-self-service || rpm -q maximo-self-service || maximo-self-service --version

2. No fixed release: DOWNGRADE to a release before 4.0 (Debian / Ubuntu)

apt-cache madison maximo-self-service sudo apt install maximo-self-service=<VERSION_BEFORE_4.0> sudo apt-mark hold maximo-self-service

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list maximo-self-service sudo dnf downgrade maximo-self-service-<VERSION_BEFORE_4.0> sudo dnf versionlock add maximo-self-service

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2005-1601?

maximo self service: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2005-1601 being exploited?

CVE-2005-1601 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2005-1601 affect?

CVE-2005-1601 affects maximo self service. Severity is medium (CVSS 5.0). MRO Maximo Self Service 4 and 5 stores certain information under the web document root using file extensions that are not processed by Tomcat, which allows remote attackers to obtain sensitive information via a direct request for the file,

How urgent is CVE-2005-1601?

Priority 36/100. No elevated risk signals yet.

Software pages

Apache Tomcat vulnerabilities

References

← Back to latest CVEs