HTML Injection through transaction memo
See original GitHub issueIn the transaction below: https://xrpcharts.ripple.com/#/transactions/7A93EE437A3FE7973900E54E35C4360E97ED174427AA1EBEDDBBCFEF66DBCB57
The initial memo content is <h1>THIS PAGE RENDERS HTML
and the HTML is rendered.
It looks like the Memo type can also have HTML Injection.
Issue Analytics
- State:
- Created 5 years ago
- Comments:7
Top Results From Across the Web
HTML Injection Tutorial: Types & Prevention with Examples
HTML Injection is just the injection of markup language code to the document of the page. Stealing other person's identity may also happen ......
Read more >SQL Injection Prevention - OWASP Cheat Sheet Series
This article provides a set of simple techniques for preventing SQL Injection vulnerabilities by avoiding these two problems. These techniques can be used...
Read more >Documentation - SolidJS · Reactive Javascript Library
A declarative, efficient and flexible JavaScript library for building user interfaces.
Read more >Attack Signatures - F5 Cloud Docs
Attack Signatures¶. Attack signatures are rules or patterns that identify attack sequences or classes of attacks on a web application and its components....
Read more >RFC 3264: An Offer/Answer Model with Session Description ...
Distribution of this memo is unlimited. ... This offer/answer model is most useful in unicast sessions where information from both participants is needed ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The sanitizer had whitelisted a few HTML tags like
h1
andb
. This whitelist has been removed, so the problem is now fixed. Thanks for reporting this!As mentioned here, confirmed it was fixed. https://github.com/ripple/ripplecharts-frontend/issues/188