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

Distribution release	Source package	Vendor state	Fixed version	Evidence
Debian trixietrixie · source	`corosync`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.4.4-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · source	`corosync`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.4.4-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · source	`corosync`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.4.4-1`	Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · source	`corosync`	Vendor fix publishedDebian records a fixed source-package version for this release.	`2.4.4-1`	Debian Security Tracker ↗Source updated 5 Oct 2026

Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available

What, why and how

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

What

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

Why

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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

Why

How

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material

Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.

None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path: a network path → Integer Overflow or Wraparound → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface: Network
Privileges required: None: unauthenticated exploitation is possible
User interaction: None
Attack complexity: Low: no specialised conditions are recorded
Security boundary: Unchanged: impact remains within the vulnerable component's security authority
Weakness ? CWE means Common Weakness Enumeration: a standard category for the underlying weakness.: CWE-190 ↗
CWE-190: Integer Overflow or Wraparound. The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
CVSS vector ? CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land: No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.

NetworkUnauthenticatedCWE-190

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2018-11734Official EUVD mapping

0 linked advisory records.

Official EUVD record ↗

CERT-FR · French · CERTFR-2022-AVI-267Multiples vulnérabilités dans Juniper Networks Junos Space

ERecord?id=CVE-2018-10373 Référence CVE CVE-2018-10534 https://www.cve.org/CVERecord?id=CVE-2018-10534 Référence CVE CVE-2018-10535 https://www.cve.org/CVERecord?id=CVE-2018-10535 Référence CVE CVE-2018-1060 https://www.cve.org/CVERecord?id=CVE-2018-1060 Référence CVE CVE-2018-1061 https://www.cve.org/CVERecord?id=CVE-2018-1061 Référence CVE CVE-2018-1064 https://www.cve.org/CVERecord?id=CVE-2018-1064 Référence CVE CVE-2018-10733 https://www.cve.org/CVERecord?id=CVE-2018-10733 Référence CVE CVE-2018-10767 https://www.cve.org/CVERecord?id=CVE-2018-10767 Référence CVE CVE-2018-10768 https://www.cve.org/CVERecord?id=CVE-2018-10768 Référence CVE CVE-2018-1084 https://www.cve.org/CVERecord?id=CVE-2018-1084 Référence CVE CVE-2018-10897 https://www.cve.org/CVERecord?id=CVE-2018-10897 Référence CVE CVE-2018-10906 https://www.cve.org/CVERecord?id=CVE-2018-10906 Référence CVE CVE-2018-1113 https://www.cve.org/CVERecord?id=CVE-2018-1113 Référence CVE CVE-2018-1116 https://www.cve.org/CVERecord?id=CVE-2018-1116 Référence CVE CVE-2018-11212 https://www.cve.org/CVERecord?id=CVE-2018-11212 Référence CVE CVE-2018-11213 https://www.cve.org/CVERecord?id=CVE-2018-11213 Référence CVE CVE-2018-11214 https://www.cve.org/CVERecord?id=CVE-2018-11214 Référence CVE CVE-2018-1122 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗

JVN iPedia · Japanese · JVNDB-2018-004110corosync における任意の整数オーバーフローの脆弱性

corosync には、整数オーバーフローの脆弱性が存在します。

Official advisory ↗

Patch and workaround

Operational remediation based on structured source evidence.

Status ? Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.: Patch available
Affected: corosync: corosync 2.4.4
Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action: Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround: No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.

Evidence and provenance

Published 12 Apr 2018 · Last source change 5 Aug 2024, 03:51 UTC · CWE-190 · Integer Overflow or Wraparound

CVE recordCVE.org · 5.1

CVSS sourceNIST NVD

EPSS source

The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.

FIRST · tracked since 2026-09-01

European sourceENISA EUVD · EUVD-2018-11734

Product sourceCNA

Remediation sourceCVE/CNA references

CWE sourceCNA

NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

1 Sep 2026, 02:42 UTC
ENISA EUVD mappingEUVD-2018-11734 was added to the official ENISA EUVD mapping for this CVE.
Before
not recorded
After
{"euvdId":"EUVD-2018-11734"}
ENISA EUVD ↗
5 Aug 2024, 03:51 UTC
Vendor guidanceAuthoritative vendor guidance changed: added patch: bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1084; added remediation: bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1084; removed vendor advisory: access.redhat.com/RHSA-2018:1169; removed vendor advisory: debian.org/dsa-4174; 2 further removals.
Before
vendor advisory: access.redhat.com/RHSA-2018:1169 · vendor advisory: debian.org/dsa-4174 · vendor advisory: security.gentoo.org/202107-01 · 1 more references
After
patch: bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1084 · remediation: bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-1084
bugzilla.redhat.com ↗
5 Aug 2024, 03:51 UTC
Affected versionsThe structured affected or fixed version information changed.
Before
corosync 2.4.4 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
After
corosync 2.4.4 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
CNA ↗
5 Aug 2024, 03:51 UTC
Remediation statusRemediation status changed from Awaiting fix to Patch available.
Before
Awaiting fix
After
Patch available
bugzilla.redhat.com ↗
5 Aug 2024, 03:51 UTC
CVSS scoreCVSS version changed from 3.0 to 3.1; the displayed base score remains 7.5.
Before
7.5 (CVSS 3.0 · CNA · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
After
7.5 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
NIST NVD ↗
5 Aug 2024, 03:51 UTC
Catalogue recordCVE added to the BlackTree catalogue.
CNA ↗

2018-04-12CVE published

2024-08-05Fixed release or patch reference recorded

ENISA EUVD · EUVD-2018-11734↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗

Technical terms and abbreviations used in this report

CVE: Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS: Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS: Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE: Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA: CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP: Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD: National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT: A computer security incident response team that publishes warnings or coordinates incident response.
PoC: Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF: Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL: Living off the land: abuse of legitimate tools or system functions during an attack.

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

Published severity in operational context

Evidence used

Compensating controls

Verification

Release-specific package status

National CERT insights
?
CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

ENISA European Vulnerability Database

EUVD-2018-11734

What, why and how

Exploit reality and attack path

Official authority intelligence

Patch and workaround

Evidence and provenance

What changed after publication