BishopFox sliver up to 1.5.42 Reverse Port Forwarding server-side request forgery

Summaryinfo

A vulnerability described as critical has been identified in BishopFox sliver up to 1.5.42. This issue affects some unknown processing of the component Reverse Port Forwarding Handler. The manipulation results in server-side request forgery. This vulnerability is reported as CVE-2025-27090. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in BishopFox sliver up to 1.5.42. It has been classified as critical. Affected is an unknown code block of the component Reverse Port Forwarding Handler. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality. CVE summarizes:

Sliver is an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. The reverse port forwarding in sliver teamserver allows the implant to open a reverse tunnel on the sliver teamserver without verifying if the operator instructed the implant to do so. The only impact that has been shown is the exposure of the server's IP address to a third party. This issue has been addressed in version 1.5.43 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

The advisory is available at github.com. This vulnerability is traded as CVE-2025-27090 since 02/18/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. The technical details are unknown and an exploit is not available.

Upgrading to version 1.5.43 eliminates this vulnerability. Applying the patch 0f340a25cf3d496ed870dae7da39eab4427bc16f is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• BishopFox

Name

• sliver

Version

• 1.5.0
• 1.5.1
• 1.5.2
• 1.5.3
• 1.5.4
• 1.5.5
• 1.5.6
• 1.5.7
• 1.5.8
• 1.5.9
• 1.5.10
• 1.5.11
• 1.5.12
• 1.5.13
• 1.5.14
• 1.5.15
• 1.5.16
• 1.5.17
• 1.5.18
• 1.5.19
• 1.5.20
• 1.5.21
• 1.5.22
• 1.5.23
• 1.5.24
• 1.5.25
• 1.5.26
• 1.5.27
• 1.5.28
• 1.5.29
• 1.5.30
• 1.5.31
• 1.5.32
• 1.5.33
• 1.5.34
• 1.5.35
• 1.5.36
• 1.5.37
• 1.5.38
• 1.5.39
• 1.5.40
• 1.5.41
• 1.5.42

License

• open-source

Website

• Product: https://github.com/BishopFox/sliver/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion