Skip to content

Wifi mouse linux #259

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.

Sign up for GitHub

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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
Open

Wifi mouse linux #259

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
34c09ec
add wifi_mouse_linux vulnerability
mission-deny-the-mission Feb 15, 2023
8d0b96a
add metadata to wifi_mouse_linux module
mission-deny-the-mission Feb 15, 2023
fa0bf4a
update secgen metadata again
mission-deny-the-mission Feb 15, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 28 additions & 0 deletions modules/vulnerabilities/unix/wifi_mouse_linux/secgen_metadata.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
<?xml version="1.0"?>
<vulnerability xmlns="http://github.com/cliffe/SecGen/vulnerability"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://github.com/cliffe/SecGen/vulnerability">
<name>WiFi Mouse Linux</name>
<author>Harry J. Hall</author>
<module_license>MIT</module_license>
<description>The Linux version of WiFi Mouse 1.7.8.5 which contains an authentication vulnerability.
WiFi Mouse is a tool for controlling a computer using a smartphone. </description>

<type>Remote control software</type>
<privilege>user_rwx</privilege>
<access>remote</access>
<platform>linux</platform>
<difficulty>medium</difficulty>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

<difficulty>high</difficulty> if they need to write their own exploit


<read_fact>server_name</read_fact>
<read_fact>strings_to_leak</read_fact>
<read_fact>leaked_filenames</read_fact>

<default_input into="string_to_leak">
<generator type="message_generator"/>
</default_input>

<default_input into="leaked_filenames">
<generator type="filename_generator">
</default_input>
</vulnerability>