# CVE-2019-4321: Weak cryptography in Intelligent Operations Center

> Weak default password policies in IBM Intelligent Operations Center allow attackers to compromise user accounts.

- **Severity:** Medium 5.9 (`CVSS:3.0/UI:N/AV:N/AC:H/C:H/S:U/A:N/PR:N/I:N/RC:C/E:U/RL:O`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-45cf-5rxq-xpqr

## What is CVE-2019-4321?

CVE-2019-4321 is a medium-severity vulnerability in IBM Intelligent Operations Center, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Intelligent Operations Center V5.1.0 - V5.2.0, IBM Intelligent Operations Center for Emergency Management V5.1.0 - V5.1.0.6, and IBM Water Operations for Waternamics V5.1.0 - V5.2.1.1 does not require that users should have strong passwords by default, which makes it easier for attackers to compromise user accounts. IBM X-Force ID: 161201.

Weakness: CWE-521 (Weak Password Requirements)

## Which versions are affected by CVE-2019-4321?

It affects 3 products.


Products: Ibm Intelligent Operations Center, Ibm Intelligent Operations Center for Emergency Management, Ibm Water Operations for Waternamics.

## How do I fix CVE-2019-4321?

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

## Is CVE-2019-4321 being exploited?

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

## Other vulnerabilities in IBM Intelligent Operations Center

- [CVE-2019-4066](https://insights.sbomify.com/CVE-2019-4066/): Privilege escalation in Intelligent Operations Center (high 8.8)
- [CVE-2019-4069](https://insights.sbomify.com/CVE-2019-4069/): File upload in Intelligent Operations Center (high 8.0)
- [CVE-2019-4419](https://insights.sbomify.com/CVE-2019-4419/): XML external entity in Intelligent Operations Center (high 7.1)
- [CVE-2019-4420](https://insights.sbomify.com/CVE-2019-4420/): Information disclosure in Intelligent Operations Center (medium 6.2)
- [CVE-2019-4067](https://insights.sbomify.com/CVE-2019-4067/): Weak cryptography in Intelligent Operations Center (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-4321 and fix it if it is affected.

What it is: CVE-2019-4321 is a medium-severity vulnerability in IBM Intelligent Operations Center, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-4321 in the wild and no public exploit code.

Affected product: IBM Intelligent Operations Center. 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-2019-4321/ (Markdown: https://insights.sbomify.com/CVE-2019-4321/index.md)
```

## Sources

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

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