Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
C
configuration
Overview
Overview
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
edx
configuration
Commits
a9dfd495
Commit
a9dfd495
authored
Sep 29, 2014
by
John Jarvis
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #1590 from edx/cg/shellshock3
Round 3 of shellshock updates
parents
22f63ea8
327f010d
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
5 deletions
+2
-5
playbooks/roles/security/tasks/security-ubuntu.yml
+2
-5
No files found.
playbooks/roles/security/tasks/security-ubuntu.yml
View file @
a9dfd495
#### Bash security vulnerability
-
name
:
Check if we are vulnerable
shell
:
executable=/bin/bash chdir=/tmp
env X='() { (a)=>\' bash -c "echo echo check"; [[ "$(cat echo)" == "check" ]] && echo "vulnerable"
shell
:
executable=/bin/bash chdir=/tmp
foo='() { echo vulnerable; }' bash -c foo
register
:
test_vuln
ignore_errors
:
yes
...
...
@@ -9,11 +9,8 @@
apt
:
name=bash state=latest update_cache=true
when
:
"
'vulnerable'
in
test_vuln.stdout"
-
name
:
Delete check file
file
:
path=/tmp/echo state=absent
-
name
:
Check again and fail if we are still vulnerable
shell
:
executable=/bin/bash
chdir=/tmp env X='() { (a)=>\' bash -c "echo echo check"; [[ "$(cat echo)" == "check" ]] && echo "vulnerable"
shell
:
executable=/bin/bash
foo='() { echo vulnerable; }' bash -c foo
when
:
"
'vulnerable'
in
test_vuln.stdout"
register
:
test_vuln
failed_when
:
"
'vulnerable'
in
test_vuln.stdout"
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment