Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Address RVD#2401 #170

Merged
merged 1 commit into from Aug 21, 2020
Merged

Address RVD#2401 #170

merged 1 commit into from Aug 21, 2020

Conversation

vmayoral
Copy link
Contributor

Our team at @aliasrobotics identified and reported in RVD#2401 the use of
unsafe yaml load (aliasrobotics/RVD#2401).

After triaging the flaw we detected that it was exploitable and could lead to
local (or remote, based on certain common user interaction) code execution.

Specifically, the flaw itself is caused by an unsafe parsing of YAML values which
happens whenever an action message is processed to be sent, and allows for the
creation of Python objects. Through this flaw in ROS, an attacker could build a
malicious payload and execute arbitrary code in Python. A PoC is available but
have decided not to disclose it for now and until this is mitigated and debs are
available.

Peer-researched and coded with @ibaiape.

Our team at @aliasrobotics identified and reported in RVD#2401 the use of 
unsafe yaml load (aliasrobotics/RVD#2401).

After triaging the flaw we detected that it was  exploitable and could lead to 
local (or remote, based on certain common user interaction) code execution.

Specifically, the flaw itself is caused by an unsafe parsing of YAML values which 
happens whenever an action message is processed to be sent, and allows for the 
creation of Python objects. Through this flaw in ROS, an attacker could build a 
malicious payload and execute arbitrary code in Python. A PoC is available but 
have decided not to disclose it for now and until this is mitigated and debs are
available.

Peer-researched and coded with @ibaiape.
@vmayoral
Copy link
Contributor Author

Ping @mjcarroll. Also a quick check (though I went fast and might've gotten it wrong for some) confirmed that this is applicable to previous ROS distros so this same patch needs to be applied to them.

@mjcarroll mjcarroll merged commit 43fe7c4 into ros:melodic-devel Aug 21, 2020
mjcarroll pushed a commit that referenced this pull request Aug 21, 2020
Our team at @aliasrobotics identified and reported in RVD#2401 the use of 
unsafe yaml load (aliasrobotics/RVD#2401).

After triaging the flaw we detected that it was  exploitable and could lead to 
local (or remote, based on certain common user interaction) code execution.

Specifically, the flaw itself is caused by an unsafe parsing of YAML values which 
happens whenever an action message is processed to be sent, and allows for the 
creation of Python objects. Through this flaw in ROS, an attacker could build a 
malicious payload and execute arbitrary code in Python. A PoC is available but 
have decided not to disclose it for now and until this is mitigated and debs are
available.

Peer-researched and coded with @ibaiape.
mjcarroll added a commit that referenced this pull request Aug 21, 2020
Our team at @aliasrobotics identified and reported in RVD#2401 the use of 
unsafe yaml load (aliasrobotics/RVD#2401).

After triaging the flaw we detected that it was  exploitable and could lead to 
local (or remote, based on certain common user interaction) code execution.

Specifically, the flaw itself is caused by an unsafe parsing of YAML values which 
happens whenever an action message is processed to be sent, and allows for the 
creation of Python objects. Through this flaw in ROS, an attacker could build a 
malicious payload and execute arbitrary code in Python. A PoC is available but 
have decided not to disclose it for now and until this is mitigated and debs are
available.

Peer-researched and coded with @ibaiape.

Co-authored-by: Víctor Mayoral Vilches <v.mayoralv@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants