bearer VS BeEF

My team and I released Bearer a couple of weeks ago, a newer open and free alternative to Brakeman to check your code for security and privacy risks. In addition to Ruby/Rails, we also cover your JS/TS code, which allows you to use a single solution for your whole Rails application.

Code security scanning tool (SAST) to discover, filter and prioritize security and privacy risks.

Code security scanning tool (SAST) to discover, filter and prioritize security and privacy risks.

Link to the Recipe https://github.com/Bearer/bearer/blob/main/pkg/classificatio...

Hi HN,

I’m Guillaume, the cofounder of Bearer, an Open Source SAST solution.

After launching a few weeks ago here on Hacker News with support for Ruby and JavaScript stacks, I’m happy to report we’ve just released a new version (v1.2) with TypeScript support!

In terms of code coverage, we use the same rules already implemented for vanilla JavaScript, but as usual, you can build your own.

The rules list is here: https://docs.bearer.com/reference/rules/

It’s a first version for TS, but we believe that thanks to the pre-existing JavaScript support it should already provide good insights.

If you have some TypeScript code, we would love for you to try it out and let us know in the comment below or on our Discord your experience and how we can improve the findings.

You can access the repo here: https://github.com/Bearer/bearer

Thank you again!

It can be challenging to keep up with security best practices. In addition to watching for vulnerability reports, you can also run regular scans on your codebase with a SAST tool like Bearer CLI. It's a free and secure way to get practical security feedback on your ruby code. Check it out on GitHub at bearer/bearer.

Using open-source tools to test open-source projects feels like a great match. It wasn't until the other day that I remembered that the team behind DEV had open-sourced the bones of the site as Forem. To make it an even better match, the stack matches up nicely with the currently supported languages included in Bearer's new free and open-source security application security testing (SAST) tool. Unlike many security tools, this one is really focused on helping devs make sense of security concerns in an actionable way.

Good news! There’s a free open-source tool that can scan your code, check for known risks, and give you a list of things that need fixing. All are sorted by how risky the code is—based on things like how sensitive the data is and how damaging a breach or leak would be. It’s called Bearer.

Ha, fun to see this again! Back before everything was HTTPS, it was fun to use the Browser Exploitation Framework (https://beefproject.com) which had a script included that did this. Though in those cases I wasn't in control of the gateway, so ARP spoofing was required to get other devices to route through me.

For example IOS WebKit has a bunch of vulnerabilities announced recently. and one of those could be used via the Browser Exploitation Framework to install malware on your phone with you just clicking the link.

Motivation is a key part, so those attacks are more theoretical than practically dangerous, however there is a class of attacks that's based on the fact that your browser can make arbitrary network connections, so unprivileged javascript can be used for some scans of your local network - for example, your router's internally accessible admin page or some vulnerability in a printer accessible in local network, as the attacker might guess commonly used models, the internal IP addresses they use by default, etc. For example, you might take a look at https://beefproject.com/

This is something that kind of annoys me; there's even a /r/rails sub-reddit specifically for Ruby on Rails stuff. Understandably Rails helped put Ruby on the map. Before Rails, Ruby was just another fringe language. Rails became massively popular, helped many startups quickly build their Web 2.0 sites, and become successful companies (ex: GitHub, LinkedIn, AirBnB, etc). Like others have said, "Rails is where the money is at". However, this posses a problem for the Ruby community: whenever Rails becomes less popular, so does Ruby. I wish the Ruby ecosystem wasn't so heavily centralized around Rails, and that we diversified our uses of Ruby a bit. There's of course Sinatra, dry-rb, Hanami, Dragon Ruby, SciRuby, and a dozen security tools written in Ruby such as Metasploit, BeFF, Arachni, and Ronin.

If you can open any webpage there then I would recommend using BeEF https://beefproject.com/

Perhaps https://beefproject.com/

If you want an example of what exploiting a browser can do, see the capabilities of the Browser Exploitation Framework (BEef): https://github.com/beefproject/beef/wiki/BeEF-modules

Take a look at BeEF framework - https://beefproject.com/ that's pretty much all the things you can do from a browser.