ecthros / pina-colada Goto Github PK

Add vulnerabilities column to the computers table

install all dependencies & setup pi for use

Extensibility can be added later - the idea(in my head) is just send tons of packets

Put more machines on the network - for example:
Windows Server 2003
Windows XP

Similar to nmap's -O option, can be extended to find computers vulnerable to MS08-67 or the like

Discussed here: https://security.stackexchange.com/questions/52070/the-overlapping-fragment-attack-using-scapy

Can we have a live demo with our own router?

Finished, but needs to be integrated

Change varchar types for ip and mac addresses to inet and macaddr data types (one of the reasons we are using postgres)

Need to :
Drop table computers
Readd table computes with different types
Modify network script to work with different types
Run and test

Keep a table of open backdoors, that sort of thing

Things like scanning for MS08 vulnerabilities, FTP anonymous, etc

Create tables for easier duplication

Need planning to decide everything that goes here

Android - definitely
Apple?

https://github.com/MooseDojo/apt2

Use flask to make a website which can profile the network and control the pi remotely

Or just keep it sniffing on all

Discussed here: https://security.stackexchange.com/questions/52070/the-overlapping-fragment-attack-using-scapy

https://github.com/henryw14/DNS-Cache-Poisoning-with-Scapy/tree/master/code

Spin up a xp box and exploit it with ms08 vulnerability

This issue is just here for creating new tables:

create table computers(
id serial,
ip varchar (50),
mac varchar(50),
ports varchar[], last_online varchar(50));

This was the computers table.

TCPKiller will kill all traffic to the web interface of the pinya, preventing the attacker from accessing it (or turning it off)

Automatically jump onto networks that are really just printers, giving us the ability to print anything.

Allow other computers on the network to connect to the postgres database

What do

To start a conversation : do we want to have different branches or do all our development on one master branch

Instead of creating new entries, figure out how to edit old ones

Figure out a mechanism for sniffing. Possible options:

1. Store all packets in some database
   Could have a table with packet number, type, etc. Good because we can have it constantly update the table.
2. Periodically write packets to some folder
   Can't view this in real time with an app

What I want to see:

Wireshark on an app

Find if they are open, then join

How often do we want to scan, should we only scan ports that were up, etc

Create some way to change how often the pi scans and wreaks havoc on the network - for example, it might be more valuable sometimes to never scan, so people on the network wouldn't notice.

The pi needs to be able to automatically detect and connect to wifi networks, and be able to change networks easily.

Get the framework started

Like nmap's -sV option, could be useful

Dependencies:

Postgres database (create script to do this automatically)
impacket from https://github.com/CoreSecurity/impacket

As we add different capabilities, managing which ones require which inputs will be tedious at best and buggy at worst - we should design a 'module' system to standardize everything and make pinya extensible (like we did for Backdoorme)

Fix this