title: Resource exhaustion via memory leak in tokio-boring
description: The tokio-boring library in version 4.0.0 is affected by a memory leak issue that can lead to excessive resource consumption and potential DoS by resource exhaustion. The set_ex_data function used by the library did not deallocate memory used by pre-existing data in memory each time after completing a TLS connection causing the program to consume more resources with each new connection.
problem types: CWE-400 Uncontrolled Resource Consumption
affected:
{
collectionURL: https://github.com/cloudflare/boring/tree/master/tokio-boring
defaultStatus: unaffected
modules: toki-boring
packageName: boring
product: tokio-boring
vendor: Cloudflare
versions:
lessThanOrEqual: 4.1.0, status: affected, version: 4.0.0, versionType: semver
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: LOW
baseScore: 5.3
baseSeverity: MEDIUM
confidentialityImpact: NONE
integrityImpact: NONE
privilegesRequired: NONE
scope: UNCHANGED
userInteraction: NONE
vectorString: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
version: 3.1
]
format: CVSS
scenarios: GENERAL