Skip to content

Cloudflare GoFlow vulnerable to a Denial of Service in the sflow packet handling package

High severity GitHub Reviewed Published Sep 30, 2022 in cloudflare/goflow • Updated Oct 2, 2023

Package

gomod github.com/cloudflare/goflow/v3 (Go)

Affected versions

< 3.4.4

Patched versions

3.4.4

Description

Impact

The sflow decode package prior to version 3.4.4 does not employ sufficient packet sanitisation which can lead to a denial of service attack. Attackers can craft malformed packets causing the process to consume huge amounts of memory resulting in a denial of service.

Specific Go Packages Affected

github.com/cloudflare/goflow/v3/decoders/sflow

Patches

Version 3.4.4 contains patches fixing this.

Workarounds

A possible workaround is to not have your goflow collector publicly reachable.

For more information

If you have any questions or comments about this advisory:

References

@mskowroncf mskowroncf published to cloudflare/goflow Sep 30, 2022
Published by the National Vulnerability Database Sep 30, 2022
Published to the GitHub Advisory Database Oct 1, 2022
Reviewed Oct 1, 2022
Last updated Oct 2, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.089%
(40th percentile)

Weaknesses

CVE ID

CVE-2022-2529

GHSA ID

GHSA-9rpw-2h95-666c

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.