twosixlabs / acsploit Goto Github PK

Hey TwoSix :)

Your slack link is dead! Any chance y'all wanna throw up a new one?

It seems I am unable to set options for the current exploit. Below is the output of several tests I ran.

(acsploit) use bombs/compression/pdf
exploit => bombs/compression/pdf
(acsploit : bombs/compression/pdf) help

Documented commands (type help <topic>):
========================================
clear  help  history  info  macro  options  quit  reset  run  set  show  use

(acsploit : bombs/compression/pdf) options

  output: file

  Output options
    filename: acsploit_output.dat
    separator: newline
    format: binary
    final_newline: False
    number_format: decimal
    template_file: None
    template_pattern: <ACSPLOIT>
    replace_first_only: False

  Exploit options
    target_payload_memory: 134217728
    time_multiplier: 1

(acsploit : bombs/compression/pdf) set time_multiplier 99
Option time_multiplier does not exist
No option set
(acsploit : bombs/compression/pdf) set bombs/compression/pdf/time_multiplier 99
Option bombs/compression/pdf/time_multiplier does not exist
No option set
(acsploit : bombs/compression/pdf) set time_multiplier=99
Usage: set [option_name] [value]

Hi,

I saw on the homepage y'all were thinking about being able to hook directly into a running program. That sounds pretty cool, what does the roadmap look like?

Hi,

I'm a Scapy maintainer, and have bumped into this project because it was linked in https://github.com/phaethon/kamene/network/dependents

I've noticed that you were using kamene. I'm assuming you were using scapy-python3 before it was renamed. Please note that kamene is NOT an official Scapy version. Quoting https://scapy.net/

An independent fork of Scapy was created from v2.2.0 in 2015, aimed at supporting only Python3 (scapy3k). The fork diverged, did not follow evolutions and fixes, and has had its own life without contributions back to Scapy. Unfortunately, it has been packaged as python3-scapy in some distributions, and as scapy-python3 on PyPI leading to confusion amongst users. It should not be the case anymore soon. Scapy supports Python3 in addition to Python2 since 2.4.0. Scapy v2.4.0 should be favored as the official Scapy code base. The fork has been renamed as kamene.

Why this is a problem

There are two issues:

• for you: you are using a version of Scapy that clearly is buggy and not maintained. Development is stopped (or sometimes a few merged PRs now and then) and it's missing many improvements and bug fixes. Moreover we had issues with the owner of this fork trying to mislead users by using a confusing name.
• for us: we get bug reports that we fixed ages ago because some people still use this fork. This wastes some of our time

I'd advise switching to scapy = the original Scapy. Note that all you need to do is change the import name.

Thanks for your time !

PS: sorry if this feels copy/pasted. It is a bit :(