Skip to content

Latest commit

 

History

History
129 lines (96 loc) · 4.42 KB

SECURITY.md

File metadata and controls

129 lines (96 loc) · 4.42 KB
Raw

Security Guidelines

Please contact us directly at security@3rd-Eden.com for any bug that might impact the security of this project. Please prefix the subject of your email with [security] in lowercase and square brackets. Our email filters will automatically prevent these messages from being moved to our spam box. All emails that do not include security vulnerabilities will be removed and blocked instantly.

In addition to a dedicated email address to receive security related reports, we also have a Hacker1 account that can be used for communicating security related issues.

You will receive an acknowledgement of your report within 24 hours of notification.

Exceptions

If you do not receive an acknowledgement within the said time frame please give us the benefit of the doubt as it's possible that we haven't seen it yet. In this case please send us a message without details using one of the following methods:

  • Give a poke on Twitter @3rdEden
  • Contact the lead developers of this project on their personal e-mails. You can find the e-mails in the git logs, for example using the following command: git --no-pager show -s --format='%an <%ae>' <gitsha> where <gitsha> is the SHA1 of their latest commit in the project.

Once we have acknowledged receipt of your report and confirmed the bug ourselves we will work with you to fix the vulnerability and publicly acknowledge your responsible disclosure, if you wish.

History

Leading control characters are not removed. This allows an attacker to bypass hostname checks and makes the extractProtocol method return false positives.

A URL with a specified but empty port can be used to bypass authorization checks.

A specially crafted URL with empty userinfo and no host can be used to bypass authorization checks.

Incorrect handling of username and password can lead to authorization bypass.

url-parse mishandles certain uses of a single (back) slash such as https:\ & https:/ and interprets the URI as a relative path. Browsers accept a single backslash after the protocol, and treat it as a normal slash, while url-parse sees it as a relative path.

Using backslash in the protocol is valid in the browser, while url-parse thinks it’s a relative path. An application that validates a url using url-parse might pass a malicious link.

  • Reporter credits
  • Fixed in: 1.5.0

The extractProtocol method does not return the correct protocol when provided with unsanitized content which could lead to false positives.

  • Reporter credits
    • Reported through our security email & Twitter interaction.
    • Twitter: @ronperris
  • Fixed in: 1.4.5

url-parse returns wrong hostname which leads to multiple vulnerabilities such as SSRF, Open Redirect, Bypass Authentication Protocol.