UBUNTU-CVE-2023-45286 (CVE-2023-45286)
Vulnerability from osv_ubuntu – Published: 2023-11-28 17:15 – Updated: 2026-05-20 15:02 – Source websiteA race condition in go-resty can result in HTTP request body disclosure across requests. This condition can be triggered by calling sync.Pool.Put with the same *bytes.Buffer more than once, when request retries are enabled and a retry occurs. The call to sync.Pool.Get will then return a bytes.Buffer that hasn't had bytes.Buffer.Reset called on it. This dirty buffer will contain the HTTP request body from an unrelated request, and go-resty will append the current HTTP request body to it, sending two bodies in one request. The sync.Pool in question is defined at package level scope, so a completely unrelated server could receive the request body.
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-go-resty-resty-dev",
"binary_version": "2.4.0-1ubuntu1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "golang-github-go-resty-resty",
"purl": "pkg:deb/ubuntu/golang-github-go-resty-resty@2.4.0-1ubuntu1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.4.0-1ubuntu1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-go-resty-resty-dev",
"binary_version": "2.10.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "golang-github-go-resty-resty",
"purl": "pkg:deb/ubuntu/golang-github-go-resty-resty@2.10.0-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.4.0-1ubuntu1",
"2.10.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-go-resty-resty-dev",
"binary_version": "2.10.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:25.10",
"name": "golang-github-go-resty-resty",
"purl": "pkg:deb/ubuntu/golang-github-go-resty-resty@2.10.0-2?arch=source\u0026distro=questing"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.10.0-1",
"2.10.0-2"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "golang-github-go-resty-resty-dev",
"binary_version": "2.10.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "golang-github-go-resty-resty",
"purl": "pkg:deb/ubuntu/golang-github-go-resty-resty@2.10.0-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"2.10.0-2"
]
}
],
"aliases": [],
"details": "A race condition in go-resty can result in HTTP request body disclosure across requests. This condition can be triggered by calling sync.Pool.Put with the same *bytes.Buffer more than once, when request retries are enabled and a retry occurs. The call to sync.Pool.Get will then return a bytes.Buffer that hasn\u0027t had bytes.Buffer.Reset called on it. This dirty buffer will contain the HTTP request body from an unrelated request, and go-resty will append the current HTTP request body to it, sending two bodies in one request. The sync.Pool in question is defined at package level scope, so a completely unrelated server could receive the request body.",
"id": "UBUNTU-CVE-2023-45286",
"modified": "2026-05-20T15:02:53Z",
"published": "2023-11-28T17:15:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2023-45286"
},
{
"type": "REPORT",
"url": "https://github.com/go-resty/resty/issues/743"
},
{
"type": "REPORT",
"url": "https://github.com/go-resty/resty/issues/739"
},
{
"type": "REPORT",
"url": "https://github.com/go-resty/resty/pull/745"
},
{
"type": "REPORT",
"url": "https://pkg.go.dev/vuln/GO-2023-2328"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-45286"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2023-45286"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.