Skip to content

Commit

Permalink
add sending output format strings lab with python format (#618)
Browse files Browse the repository at this point in the history
  • Loading branch information
jasinner authored Oct 14, 2024
1 parent 98ca38a commit 74fae71
Showing 1 changed file with 136 additions and 0 deletions.
136 changes: 136 additions & 0 deletions docs/labs/format-strings.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,136 @@
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="https://best.openssf.org/assets/css/style.css">
<link rel="stylesheet" href="checker.css">
<script src="js-yaml.min.js"></script>
<script src="checker.js"></script>
<link rel="license" href="https://creativecommons.org/licenses/by/4.0/">


<script id="expected0" type="plain/text">
return '{format_string}, {event.level}'.format(format_string=user_input, event=event)
</script>

<!-- Full pattern of correct answer -->
<script id="correct0" type="plain/text">
\s*return\s'\{format_string\},\s\{event\.level\}'\.format\(format_string=user_input,\sevent=event\)\s*
</script>

<script id="info" type="application/yaml">
---
- absent: "user_input"
text: Make sure the user_input is included in the replacement fields passed to the format function
examples:
- - "'some format'.format(user_input=user_input)"
- - "'some format'.format(user_input)"
- absent: "event"
text: Make sure the event is included in the replacement fields passed to the format function
examples:
- - "'some format'.format(user_input=user_input, event=event)"
- - "'some format'.format(user_input, event)"
- absent: \{(0|format_string)\}
text: Make sure the braces for the format_string replacement field are in the format string
examples:
- - "'{event}'.format(format_string=user_input)"
- - "'{0}.format(user_input)"
- absent: \{(1|event)\}
text: Make sure the braces for the event replacement field are in the format string
examples:
- - "'{format_string}, {event.level}'.format(format_string=user_input, event=event)"
- - "'{0}, {1.level}'.format(user_input, event)"
- absent: \{(1\.level|event\.level)\}
text: Make sure the level attribute of the event replacement field is in the format string
examples:
- - "'{format_string}, {event.level}'.format(format_string=user_input, event=event)"
- - "'{0}, {1.level}'.format(user_input, event)"
# debug: true
</script>
</head>
<body>
<!-- For GitHub Pages formatting: -->
<div class="container-lg px-3 my-5 markdown-body">
<h1>Lab Exercise Format Strings and Templates</h1>
<p>
This is a lab exercise on developing secure software.
For more information, see the <a href="introduction.html" target="_blank">introduction to
the labs</a>.

<p>
<h2>Task</h2>
<p>
<b>Practice using string templates in a secure way.</b>

<p>
<h2>Background</h2>
<p>
In this exercise, we'll adjust our string formatting so that it doesn't allow a user to control
the <a href="https://docs.python.org/3/tutorial/inputoutput.html#the-string-format-method"><tt>
format string</tt></a>. If a user can control the <tt>format string</tt> they can access
variables which they shouldn't. Particularly if those variable's values can be returned to the user
as output, it could lead to information disclosure beyond what was intended by the developer.

<p>
<h2>Task Information</h2>
<p>

<p>
Please change the code below so the string formatting cannot disclose arbitrary
program values. The server-side program is written in Python and allows a user to specify a
<tt>format string</tt> to control the output format of an event.

<p>
You could adjust the program so that it only formats the event, and does not include any user input,
However it is considered safe to include user input in the output as long as they cannot control
the <tt>format string</tt> itself.

<p>
Adjust the value returned by the <tt>format_event</tt> function so the the user controlled
<tt>user_input</tt> variable is only used as a
<a href="https://docs.python.org/3/library/string.html#format-string-syntax"><tt>replacement field</tt></a>
and is not used as the <tt>format string</tt>.

<p>
Use the “hint” and “give up” buttons if necessary.

<p>
<h2>Interactive Lab (<span id="grade"></span>)</h2>
<p>
<form id="lab">
<pre><code
> # Application configuration which should be kept secret from a user
CONFIG = {
'SECRET_KEY': 'super secret key'
}

# A event object with a single attribute used by the malicious format string to gain access to the
# secret application configuration below
class Event(object):
def __init__(self, level):
self.level = level

def format_event(user_input, event):
<input id="attempt0" type="text" size="60" spellcheck="false" value=" return user_input.format(event=event)">

event = Event('level')
format_event('{event.__init__.__globals__[CONFIG][SECRET_KEY]}', event)
</code></pre>
<button type="button" class="hintButton">Hint</button>
<button type="button" class="resetButton">Reset</button>
<button type="button" class="giveUpButton">Give up</button>
<br><br>
<p>
<i>This lab was developed by Jason Shepherd at
<a href="https://access.redhat.com"
>Red Hat</a>.</i> with an modified version of the example code from Armin Ronacher's
<a href="https://lucumr.pocoo.org/2016/12/29/careful-with-str-format/">Be Careful with Python's New-Style String Format</a> article.
<br><br>
<p id="correctStamp" class="small">
<textarea id="debugData" class="displayNone" rows="20" cols="65" readonly>
</textarea>
</form>
</div><!-- End GitHub pages formatting -->
</body>
</html>

0 comments on commit 74fae71

Please sign in to comment.