Data center: Ashburn, VA

Telegram Chat : MBHH_x86

Email Us: Help@mobilehackerforhire.com

Mobile Hacker For Hire

Safeurl HTTP library brings SSRF protection to Go applications

Table of Contents

Prizes offered to anyone who can bypass the library and capture the flag

Safeurl HTTP library brings SSRF protection to Go applications

A new open source library designed to thwart server-side request forgery (SSRF) attacks plugs a significant gap in Go developers’ armory, according to its architects.

Safeurl, a one-line drop-in replacement for Go’s native , validates incoming HTTP requests against allow and block lists, as well as defending against DNS rebinding attacks.

“All the heavy work of parsing, validating, and issuing requests is done by the library,” said Doyensec security engineers and Safeurl creators Viktor Chuchurski and Alessandro Cotto in a blog post.

“The library works out-of-the-box with minimal configuration, while providing developers the customizations and filtering options they might need. Instead of fighting to solve application security problems, developers should be free to focus on delivering quality features to their customers.”

SafeCURL inspiration

Chuchurski and Cotto said they wanted to give Go applications the same protection afforded to counterparts written in other languages through SafeCURL and (the identically named but differently capitalized) SafeURL.

“Our clients were asking for recommendations on a Go-specific solution to mitigate [SSRF] attacks,” the pair told The Daily Swig. “There was nothing built specifically for Go so we took on the challenge.”

Read more of the latest dev stack tech news and analysis

SSRF exploits involve inducing server-side applications into make requests to unintended locations.

“It is common for modern web applications to make HTTP requests, but a secure implementation can be quite difficult,” continued Chuchurski and Cotto.

“We hope our library will satisfy that need. It was designed with ease of use in mind and protects apps simply with its drop-in default settings.”

Erring on the side of caution

Safeurl blocks all traffic to private or reserved IP addresses by default, as prescribed by RFC1918.

“It’s easier (and safer) to explicitly set allowed destinations, as opposed to having to deal with updating a blocklist in today’s ever-expanding threat landscape,” explained the blog post.

The safeurl.Config can be used to customize the safeurl.Client to set , , , , , , , , , and .

The open source library allows configuration of HTTP redirects, cookie jar settings, and request timeouts.

DNS rebinding attacks, which exploit mismatches in DNS responses between two or more consecutive HTTP requests, are repelled by performing allow/block list validations on the IP address used to make the HTTP request via Go’s net/dialer package and the hook.

Swag, gadgets up for grabs

The researchers have created a Capture the Flag (CTF) challenge for Safeurl with “swag and some cool gadgets” on offer to anyone who succeeds.

“We’re confident in our code and the CTF is putting that confidence to the test,” said Chuchurski and Cotto. “It’s a simple web server with an SSRF vulnerability.

“The twist is that the point where the vulnerability is triggered is protected by the ‘safeurl’ library. If anyone is able to find a bypass, they’ll find further instructions.”

YOU MIGHT ALSO LIKE Critical IP spoofing bug patched in Cacti

Leave a Reply

Your email address will not be published. Required fields are marked *

error: Content is protected !!