SuperTokens Community
DOMPurify
Our great sponsors
SuperTokens Community | DOMPurify | |
---|---|---|
113 | 42 | |
11,872 | 12,731 | |
4.8% | - | |
9.4 | 8.5 | |
about 15 hours ago | 11 days ago | |
Java | JavaScript | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
SuperTokens Community
-
Auth0 increases price by 300%
Checkout https://supertokens.com/ - open source alternative to Auth0. It has a lot of free features and if you self host it, it's free at any scale. For our managed service, it's still far cheaper compared to Auth0.
-
🚀 Top 12 Open Source Auth Projects Every Developer Should Know 🔑
SuperTokens
-
Free auth products you can start using today
Building auth for your SaaS product shouldn't be hard. Try these free solutions for your next project 👇 http://supabase.com/auth free up to 50k users/month http://firebase.google.com/products/auth free up to 50k users/month http://aws.amazon.com/cognito free up to 50k users/month http://clerk.com free up to 10k users/month http://kinde.com free up to 7.5k users/month https://www.descope.com free up to 7.5k users/month https://supertokens.com free up to 5k users/month Save for later! Besides users/month what other features do you look for in auth products?
- What is the best way to implement authentication that provides Google Auth, Facebook Auth, etc.
-
The Developer-First Security Week free event (Aug 7-11)
The Developer-First Security Week event is on August 7-11. The theme is shifting left with a security mindset with top expert speakers from Snyk, BoxyHQ, Microsoft, Google, Gitlab, Bearer, SuperTokens, Cerbos, and more...Come learn with us as the speakers dive into complex topics on Authorization, Authentication, Data Privacy.
-
What is the easiest authentication method with nodejs currently available?
Supertokens dont reinvent, just reuse
-
Top open source security devtools you need to know about
GitHub: https://github.com/supertokens/supertokens-core Website: https://supertokens.com/
-
Introducing Pezzo: Open-source AI Development Toolkit 🚀
Signing up - You're not actually signing up to anything. Supertokens (open source auth provider) is running locally on your machine. It's just a means for you to be able to have an account (and soon invite others to your project to collaborate together). The data doesn't leave your computer.
- Supertokens: Open-Source Alternative to Auth0 / Firebase Auth / AWS Cognito
DOMPurify
-
JavaScript Libraries for Implementing Trendy Technologies in Web Apps in 2024
DOMPurify
- Lessons from open-source: Use window.trustedTypes to prevent DOM XSS.
-
Launched my Social Media website for lonely people living abroad, all thanks to NextJS!
I saw that some people were injecting alerts. If you haven't fixed it yet, consider using something like DOMPurify to sanitize the HTML input before posting it to the db.
-
Mastering DOM manipulation with vanilla JavaScript
You mean from this article "Sanitize HTML strings"? https://phuoc.ng/collection/html-dom/sanitize-html-strings/
Yeah, that article really shouldn't imply that sanitization is "that easy". It does at least mention https://github.com/cure53/DOMPurify at the end but it should LOUDLY argue against attempting to write this particular thing yourself and promote that exclusively in my opinion.
-
Crafting a Dynamic Blog with Next.js 13 App Directory
It is highly recommended to use an XSS Sanitizer like DOMPurify to sanitize HTML and prevent XSS attacks. For Next.js projects, which prominently feature server-side rendering, Isomorphic DOMPurify is especially valuable. It offers a seamless sanitization process across both server and client, ensuring consistent HTML sanitization in environments like Next.js where a native server-side DOM isn't present.
-
Mitigating DOM clobbering attacks in JavaScript
Note: We’ve used DOMPurify to sanitize the HTML in the above code block. You can install it in Node.js with npm install dompurify. Include it in your HTML with .
-
5 injection vulnerabilities hackers don't want developers to know about (and how to prevent them)
body, input.value property, or body are all different). If you need to insert untrusted input into raw HTML, use a well-tested sanitizer such as DOMPurify.
Setting a strong Content Security Policy without
unsafe-inline
orunsafe-eval
in thescript-src
ordefault-src
directives is an effective defense-in-depth) measure to prevent modern browsers from executing attacker code even if the attacker is able to insert</code> elements into the page.</p> <p><strong>3. HTTP API injection</strong></p> <p>RESTful APIs, GraphQL, and other HTTP-based APIs are ubiquitous. When a web application makes an API call to another service, injection vulnerabilities are possible when that request includes untrusted input.</p> <p>Consider a contrived example in which a web app integrates with a payments service that has a REST API endpoint for creating a subscription: <code>POST /subscriptions/{product_id}?price_usd=<price></code> where <code>price_usd</code> is optional, and a pre-configured price is used if omitted. If an attacker controls the value of <code>product_id</code> and passes a value of <code>desired_product_id?price_id=0</code>, the web app would end up making a request to <code>POST /subscriptions/desired_product_id?price_id=0</code>, which would allow the attacker to sign up for a free subscription.</p> <p>In JavaScript, the standard way to sanitize untrusted inputs in URL paths is <a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent"><code>encodeURIComponent</code></a>, which replaces problematic characters such as <code>?</code> and <code>/</code> with safe percent-encoded sequences. When inserting untrusted input into URL query parameters, <a href="https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams/URLSearchParams"><code>new URLSearchParams(queryParams)</code></a> provides a convenient, safe interface for building a query string from a JavaScript object of key-value pairs.</p> <p><strong>4. Shell injection</strong></p> <p>Backend APIs sometimes need to execute external commands on the machine where they run. Consider an API that performs <a href="https://en.wikipedia.org/wiki/WHOIS">WHOIS</a> lookups for a requested domain by executing the <code>whois</code> command locally.</p> <p>Consider the following <strong>vulnerable</strong> Node.js code:</p> <pre><code>const whois = child_process.execSync(`whois ${whoisRequest.domain}`); </code></pre> <p>If an attacker can pass the domain <code>reddit.com && rm -rf /</code>, the backend will execute the command <code>whois reddit.com && rm -rf /</code>. The <a href="https://nodejs.org/api/child_process.html#child_processexecsynccommand-options"><code>child_process.execSync</code></a> function passes the command string to the shell (<code>/bin/sh</code> by default on Linux), which parses <code>&& rm -rf /</code> as a subsequent command to wipe the filesystem.</p> <p>To avoid this issue, <strong>never pass untrusted input to a shell</strong>. Instead, use an interface such as <a href="https://nodejs.org/api/child_process.html#child_processexecfilesyncfile-args-options"><code>child_process.execFileSync</code></a> that executes a specific binary (which shouldn't be a shell!) and passes arguments <em>as an array</em>:</p> <pre><code>const whois = child_process.execFileSync("whois", [whoisRequest.domain]); </code></pre> <p>Now, even if the user passes a domain <code>reddit.com && rm -rf /</code>, that entire string will be passed as the command-line argument to <code>whois</code>, which will exit with an error but will not cause any harmful side-effects. Perhaps an even better solution would be to use a library to perform WHOIS queries without needing to execute a separate command.</p> <p>Astute readers may point out that validating the domain against a regex would also likely prevent shell injection in this case. However, avoiding the possibility of shell injection by using a safe interface that keeps untrusted input away from a shell's command parser is a more robust solution that avoids shell injection in all cases.</p> <p><strong>5. Path traversal</strong></p> <p>Finally, a path traversal vulnerability arises when an untrusted input is inserted into a filesystem path, which can cause the wrong file to be read or even written. Consider a backend API that reads a file at the path <code>/teams/${team_id}/${report_name}.csv</code>. If an attacker controls the value of <code>report_name</code> but not <code>team_id</code>, they could pass a <code>report_name</code> of <code>../other_team_id/private.</code> This would cause the file <code>/teams/team_id/../other_team_id/private.csv</code> (resolved to <code>/teams/other_team_id/private.csv</code>) to be read, leaking data from a different team.</p> <p>To avoid path traversal vulnerabilities, <strong>never use untrusted input in file or directory names</strong>. It's safest always to control the names of files and directories, including IDs that you generate and control (e.g., UUIDs, KSUIDs, etc.). If the name of a file or directory absolutely <em>must</em> be derived from untrusted input, consider hashing it (e.g., using SHA-256) or at least encoding it into a format that doesn't include dots or slashes (e.g., <a href="https://datatracker.ietf.org/doc/html/rfc4648#section-5">URL-safe base64</a>).</p> <p>​</p> <p>Know of good Node.js libraries for avoiding injection vulnerabilities? Let folks know in the comments!</p> </div><!-- SC_ON -->
-
Is it harder to build and maintain web applications using vanilla js or react?
https://stackoverflow.com/questions/43584685/input-sanitization-in-reactjs https://www.npmjs.com/package/dompurify
-
Six security risk of user input in ruby code
If you're using an external view engine, or a javascript framework like react in addition to your ruby backend, you can rely on similar sanitization methods like the DOMPurify library.
-
Wat
You shouldn't roll your own for this. From what I've had to do web-wise, here's a few tools.
First, for the APIs, you need documentation: https://swagger.io/
From which you can generate JSON schemas and use those to validate in the browser and on the backend. https://www.npmjs.com/package/jsonschema
As well you should be writing a few more schemas for your application state and leverage the regex validation of your input components...
Speaking of which, you also need to sanitize out some potentially nasty input. https://www.npmjs.com/package/dompurify
Obviously this isn't everything and not perfect, but a lot of this tedium can be automated away if you have a few good examples of the happy path and some basic tests in place to prevent quick and dirty changes from poking holes in these layers.
What are some alternatives?
Ory Kratos - Next-gen identity server replacing your Auth0, Okta, Firebase with hardened security and PassKeys, SMS, OIDC, Social Sign In, MFA, FIDO, TOTP and OTP, WebAuthn, passwordless and much more. Golang, headless, API-first. Available as a worry-free SaaS with the fairest pricing on the market!
sanitize-html - Clean up user-submitted HTML, preserving whitelisted elements and whitelisted attributes on a per-element basis. Built on htmlparser2 for speed and tolerance
Keycloak - Open Source Identity and Access Management For Modern Applications and Services
js-xss - Sanitize untrusted HTML (to prevent XSS) with a configuration specified by a Whitelist
authentik - The authentication glue you need.
HtmlSanitizer - Cleans HTML to avoid XSS attacks
authelia - The Single Sign-On Multi-Factor portal for web apps
xss-filters
springboot-keycloak-openldap - The goal of this project is to create a simple Spring Boot REST API, called simple-service, and secure it with Keycloak. Furthermore, the API users will be loaded into Keycloak from OpenLDAP server.
Next.js - The React Framework
zitadel - ZITADEL - The best of Auth0 and Keycloak combined. Built for the serverless era.
isomorphic-dompurify - Use DOMPurify on server and client in the same way