# CVE-2015-1933: Information disclosure in n/a

> Missing autocomplete attribute on password fields allows attackers to steal credentials from unattended workstations, leading to unauthorized access.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Oct 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-54c6-jq4h-qxx7

## What is CVE-2015-1933?

CVE-2015-1933 is a low-severity vulnerability in Ibm Maximo Asset Management, published on 4 Oct 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

IBM Maximo Asset Management 7.1 through 7.1.1.13, 7.5.0 before 7.5.0.8 IFIX001, and 7.6.0 before 7.6.0.1 IFIX001; Maximo Asset Management 7.5.x before 7.5.0.8 IFIX001 and 7.6.0 before 7.6.0.1 IFIX001 for SmartCloud Control Desk; and Maximo Asset Management 7.1 through 7.1.1.13 and 7.2 for Tivoli IT Asset Management for IT and certain other products do not have an off autocomplete attribute for the password field, which makes it easier for remote attackers to obtain access by leveraging an unattended workstation.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-1933?

It affects 13 products.


Products: Ibm Change and Configuration Management Database, Ibm Maximo Asset Management, Ibm Maximo Asset Management Essentials, Ibm Maximo for Energy Optimization, Ibm Maximo for Government, Ibm Maximo for Life Sciences, Ibm Maximo for Nuclear Power, Ibm Maximo for Oil and Gas, Ibm Maximo for Transportation, Ibm Maximo for Utilities, Ibm Smartcloud Control Desk, Ibm Tivoli Asset Management for It, Ibm Tivoli Service Request Manager.

## How do I fix CVE-2015-1933?

No fix has been published for CVE-2015-1933 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-1933 being exploited?

There is no known exploitation of CVE-2015-1933 in the wild and no public exploit code.

## Other vulnerabilities in Ibm Maximo Asset Management

- [CVE-2013-3323](https://insights.sbomify.com/CVE-2013-3323/): Privilege escalation in n/a (critical 9.8)
- [CVE-2015-0104](https://insights.sbomify.com/CVE-2015-0104/): Code injection in n/a (high 8.8)
- [CVE-2012-0714](https://insights.sbomify.com/CVE-2012-0714/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-2183](https://insights.sbomify.com/CVE-2012-2183/): Auth bypass in n/a (medium 6.8)
- [CVE-2012-2184](https://insights.sbomify.com/CVE-2012-2184/): Auth bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1933 and fix it if it is affected.

What it is: CVE-2015-1933 is a low-severity vulnerability in Ibm Maximo Asset Management, published on 4 Oct 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-1933 in the wild and no public exploit code.

Affected product: Ibm Maximo Asset Management. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-1933/ (Markdown: https://insights.sbomify.com/CVE-2015-1933/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-1933
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-1933
- OSV: https://osv.dev/vulnerability/CVE-2015-1933

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-1933/
Summaries are generated and may contain mistakes; the official description above is the record.