# CVE-2023-45187: IBM Engineering Lifecycle Optimization - Publishing session fixation

> Authenticated users can impersonate others due to session fixation caused by sessions not being invalidated after logout.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-r5hh-fv95-jjxp

## What is CVE-2023-45187?

CVE-2023-45187 is a medium-severity authentication bypass vulnerability in IBM Engineering Lifecycle Optimization - Publishing, published on 9 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Engineering Lifecycle Optimization - Publishing 7.0.2 and 7.0.3 does not invalidate session after logout which could allow an authenticated user to impersonate another user on the system.  IBM X-Force ID:  268749.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

## Which versions are affected by CVE-2023-45187?

It affects 1 product.


Products: Ibm Engineering Lifecycle Optimization.

## How do I fix CVE-2023-45187?

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

## Is CVE-2023-45187 being exploited?

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

## Other vulnerabilities in IBM Engineering Lifecycle Optimization - Publishing

- [CVE-2023-45191](https://insights.sbomify.com/CVE-2023-45191/): IBM Engineering Lifecycle Optimization information disclosure (high 7.5)
- [CVE-2021-29774](https://insights.sbomify.com/CVE-2021-29774/): Privilege escalation in Engineering Lifecycle Optimization (high 7.5)
- [CVE-2021-29786](https://insights.sbomify.com/CVE-2021-29786/): Information disclosure in Engineering Lifecycle Optimization (medium 6.5)
- [CVE-2024-52890](https://insights.sbomify.com/CVE-2024-52890/): IBM Engineering Lifecycle Optimization - Publishing cross-site scripting (medium 6.1)
- [CVE-2021-29673](https://insights.sbomify.com/CVE-2021-29673/): Cross-site scripting in Engineering Lifecycle Optimization (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45187 and fix it if it is affected.

What it is: CVE-2023-45187 is a medium-severity authentication bypass vulnerability in IBM Engineering Lifecycle Optimization - Publishing, published on 9 Feb 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45187 in the wild and no public exploit code.

Affected product: IBM Engineering Lifecycle Optimization - Publishing. 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-2023-45187/ (Markdown: https://insights.sbomify.com/CVE-2023-45187/index.md)
```

## Sources

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

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