From 628046738b0e4f410c639dd4844925ff044c79d2fb14b0e42722f1bee733f1ad Mon Sep 17 00:00:00 2001 From: Nicholas Johnson Date: Mon, 27 May 2024 00:00:00 +0000 Subject: Fix tons of links --- content/entry/oxen-security-fail.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'content/entry/oxen-security-fail.md') diff --git a/content/entry/oxen-security-fail.md b/content/entry/oxen-security-fail.md index a32abef..fc750fe 100644 --- a/content/entry/oxen-security-fail.md +++ b/content/entry/oxen-security-fail.md @@ -6,11 +6,11 @@ draft: false --- Lately I've been doing research on the Oxen Privacy Tech Foundation and their various projects. On 19 September while looking at Session, I noticed getsession.org was missing the [Strict-Transport-Security header](https://securityheaders.com/?q=https%3A%2F%2Fgetsession.org&followRedirects=on). So I decided to also check the security headers for [oxen.io](https://securityheaders.com/?q=https%3A%2F%2Foxen.io&followRedirects=on), [lokinet.org](https://securityheaders.com/?q=https%3A%2F%2Flokinet.org&followRedirects=on), and [optf.ngo](https://securityheaders.com/?q=https%3A%2F%2Foptf.ngo&followRedirects=on) and what do you know, they're also missing HTTP security headers. -The download links for each project are all vulnerable to network-level [man-in-the-middle attacks](https://www.wikipedia.org/wiki/Man-in-the-middle_attack). They also load external resources with no CSP header. They're all missing X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a Permissions-Policy. This is the web security equivalent of leaving your front door open. +The download links for each project are all vulnerable to network-level [man-in-the-middle attacks](https://en.wikipedia.org/wiki/Man-in-the-middle_attack). They also load external resources with no CSP header. They're all missing X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and a Permissions-Policy. This is the web security equivalent of leaving your front door open. When I noticed the lack of security headers on getsession.org, I emailed support@getsession.org informing them of the issue the same day. Over a week later, it's still not fixed and I have no response. How long has their website been insecure like this? I'm left wondering whether I should take OPTF and their work seriously. How can crypto projects focused primarily on privacy and security overlook basic web security? OPTF has some explaining to do. -Their sites may have other security vulnerabilities I'm unaware of. I'm no web pentester and I have no interest in pursuing it further. I may ask a pen tester friend of mine to look into it for me. I'm going to contact OPTF directly through their [contact form](https://optf.ngo/contact-us/) about what all I've already found. I'll update this entry later once they respond. +Their sites may have other security vulnerabilities I'm unaware of. I'm no web pentester and I have no interest in pursuing it further. I may ask a pen tester friend of mine to look into it for me. I'm going to contact OPTF directly through their [contact form](https://optf.ngo/contact-us) about what all I've already found. I'll update this entry later once they respond. # Update (2021-10-02): I received a response the same day I contacted the OPTF. They let me know my original email to Session went to spam which is why they didn't see it. It probably got filtered because I put "URGENT" in the subject line. The issue was resolved by the next day and the CTO (Kee Jefferys) thanked me for the feedback. -- cgit v1.2.3