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'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.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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'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. (CVE-2023-45286)

Note that Nessus relies on the presence of the package as reported by the vendor.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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'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. (CVE-2023-45286)

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the b5e22ec5-bc4b-11ee-b0b5-b42e991fc52e advisory.

  - 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'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. (CVE-2023-45286)

  - The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other     products, allows remote attackers to bypass integrity checks such that some packets are omitted (from the     extension negotiation message), and a client and server may consequently end up with a connection for     which some security features have been downgraded or disabled, aka a Terrapin attack. This occurs because     the SSH Binary Packet Protocol (BPP), implemented by these extensions, mishandles the handshake phase and     mishandles use of sequence numbers. For example, there is an effective attack against SSH's use of     ChaCha20-Poly1305 (and CBC with Encrypt-then-MAC). The bypass occurs in chacha20-poly1305@openssh.com and     (if CBC is used) the -etm@openssh.com MAC algorithms. This also affects Maverick Synergy Java SSH API     before 3.1.0-SNAPSHOT, Dropbear through 2022.83, Ssh before 5.1.1 in Erlang/OTP, PuTTY before 0.80,     AsyncSSH before 2.14.2, golang.org/x/crypto before 0.17.0, libssh before 0.10.6, libssh2 through 1.11.0,     Thorn Tech SFTP Gateway before 3.4.6, Tera Term before 5.1, Paramiko before 3.4.0, jsch before 0.2.15,     SFTPGo before 2.5.6, Netgate pfSense Plus through 23.09.1, Netgate pfSense CE through 2.7.2, HPN-SSH     through 18.2.0, ProFTPD before 1.3.8b (and before 1.3.9rc2), ORYX CycloneSSH before 2.3.4, NetSarang     XShell 7 before Build 0144, CrushFTP before 10.6.0, ConnectBot SSH library before 2.2.22, Apache MINA sshd     through 2.11.0, sshj through 0.37.0, TinySSH through 20230101, trilead-ssh2 6401, LANCOM LCOS and     LANconfig, FileZilla before 3.66.4, Nova before 11.8, PKIX-SSH before 14.4, SecureCRT before 9.4.3,     Transmit5 before 5.10.4, Win32-OpenSSH before 9.5.0.0p1-Beta, WinSCP before 6.2.2, Bitvise SSH Server     before 9.32, Bitvise SSH Client before 9.33, KiTTY through 0.76.1.13, the net-ssh gem 7.2.0 for Ruby, the     mscdex ssh2 module before 1.15.0 for Node.js, the thrussh library before 0.35.1 for Rust, and the Russh     crate before 0.40.2 for Rust. (CVE-2023-48795)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Type	Severity
256103	Linux Distros Unpatched Vulnerability : CVE-2023-45286	Nessus	Misc.	Local	medium
421532	SCA: security update for github.com/go-resty/resty/v2 (GHSA-xwh9-gc39-5298)	Tenable Cloud Security	SCA Checks	Local	medium
421532	SCA: security update for github.com/go-resty/resty/v2 (GHSA-xwh9-gc39-5298)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium
189707	FreeBSD : rclone -- Multiple vulnerabilities (b5e22ec5-bc4b-11ee-b0b5-b42e991fc52e)	Nessus	FreeBSD Local Security Checks	Local	medium

Detections

Analytics

CVE-2023-45286

medium

Tenable Plugins

medium

medium

medium

medium