Regular Expression Security Cheatsheet - Revision history

Dominique RIGHETTO: Project cleanup

2019-07-15T14:51:46Z

Project cleanup

2016-10-09T16:41:23Z

‎Cheatsheet

2016-10-09T16:41:11Z

‎Regular Expression Security Cheatsheet

2016-10-09T16:40:37Z

‎Regular Expression Security Cheatsheet

2016-10-09T16:40:13Z

2016-10-05T12:11:40Z

‎Introduction

2016-10-05T12:11:32Z

‎Introduction

2016-10-05T12:11:18Z

‎Introduction

2016-10-05T12:11:12Z

‎Cheatsheet

2016-10-05T12:10:51Z

‎Other Cheatsheets

← Older revision		Revision as of 14:51, 15 July 2019
Line 27:		Line 27:
	Vladimir Ivanov<br>		Vladimir Ivanov<br>
	[http://twitter.com/httpsonly @httpsonly]		[http://twitter.com/httpsonly @httpsonly]
		+
		+	{{taggedDocument\| type=delete\| comment=Tagged via fixme/delete.}}

@@ Line 8: / Line 8: @@
 == Cheatsheet ==
-Here is a link to GitHub RegEx repository:
+Here is a link to the GitHub RegEx repository:
 === [https://github.com/attackercan/regexp-security-cheatsheet https://github.com/attackercan/regexp-security-cheatsheet] ===
 <br><br>

@@ Line 3: / Line 3: @@
 == Introduction ==
-This cheatsheet can be effectively used by security specialists and programmers to reveal unwanted constructions in regular expressions, which can cause bypass of written rules.<br>
+This cheatsheet can be effectively used by security specialists and programmers to reveal unwanted constructions in regular expressions. This can cause bypass of intended validation rules.<br>
 <br>

← Older revision		Revision as of 16:40, 9 October 2016
Line 4:		Line 4:

	This cheatsheet can be effectively used by security specialists and programmers to reveal unwanted constructions in regular expressions, which can cause bypass of written rules.<br>		This cheatsheet can be effectively used by security specialists and programmers to reveal unwanted constructions in regular expressions, which can cause bypass of written rules.<br>
−	~~Despite original work was focused on finding "weak places" in regular expressions of Intrusion Detection Systems (WAFs), it can be effectively applied to any other code.~~
−	~~<br>~~
	<br>		<br>

@@ Line 10: / Line 10: @@
 == Cheatsheet ==
-Due to the fact, that OWASP's MediaWiki styling could not compete to Markdown, I decided not to include full table here, but provide a link to GitHub repository instead:
+Here is a link to GitHub RegEx repository:
 === [https://github.com/attackercan/regexp-security-cheatsheet https://github.com/attackercan/regexp-security-cheatsheet] ===
 <br><br>
@@ Line 16: / Line 16: @@
 == SAST ==
-In order to save time for security practitioners, Static Application Security Testing tool was written. You can use the following code to analyse all regular expressions from your PHP project:<br>
+In order to save time for security practitioners, Static Application Security Testing tool was written. You can use the following code to analyze all regular expressions from your project:<br>
 <code>
 grep -iorP "reg_\w+\s*\((\s*['\"](.*?)['\"])," * > regexp.txt && php index.php --file="./regexp.txt"

@@ Line 3: / Line 3: @@
 == Introduction ==
-This cheatsheet can be effectively used by security specialists and programmers to reveal unwanted constructions in their regular expressions, which can cause bypass of their rules.<br>
+This cheatsheet can be effectively used by security specialists and programmers to reveal unwanted constructions in regular expressions, which can cause bypass of their rules.<br>
 Despite original work was focused on finding "weak places" in regular expressions of Intrusion Detection Systems (WAFs), it can be effectively applied to any other code.
 <br>

← Older revision		Revision as of 12:10, 5 October 2016
Line 28:		Line 28:
	Vladimir Ivanov<br>		Vladimir Ivanov<br>
	[http://twitter.com/httpsonly @httpsonly]		[http://twitter.com/httpsonly @httpsonly]
−
−	~~== Other Cheatsheets ==~~
−	~~{{Cheatsheet_Navigation}}~~
−
−	~~[[Category:Cheatsheets]]~~