Skip to content

Add Recent Changes section to README #26

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 1 commit into
base: master
Choose a base branch
from
Open

Add Recent Changes section to README #26

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
18 changes: 9 additions & 9 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,6 @@
# Exploits
Miscellaneous proof of concept exploit code written at Xiphos Research for testing purposes.

## Current Exploits (index may be out of date)

* phpMoAdmin Remote Code Execution (CVE-2015-2208)
* LotusCMS Remote Code Execution (OSVDB-75095)
* ElasticSearch Remote Code Execution (CVE-2015-1427)
Expand Down Expand Up @@ -33,24 +31,26 @@ Miscellaneous proof of concept exploit code written at Xiphos Research for testi
* wipgpwn - Remote Root Exploit for WePresent WiPG-1000,1500,2000 devices
* dloser - D-Link DNS-320/330/350/x Remote Root Exploit
* TBA

## Infrequently Asked Questions.

1. Why is there no "leet zerodays" in here?

Because some of our researchers don't believe in killing bugs prematurely, and the unofficial policy on disclosure is that it is at the sole discretion of the person who finds the bug.
2. Why don't you just write metasploit modules?

Reasons, namely, "ruby", amongst other things. Also, other people who are actually getting paid by Rapid7 to do such things can do such things :)
3. Why are there some old bugs in here?

The public exploits available for them were unreliable/untrustworthy/rubbish and better ones were called for, or, they are parts of ongoing experiments into various methods to make them more reliable/stealthy/whatever.

## Licence
See individual exploits for their respective licences.

## Bug Reports
We take the quality of our exploit code very seriously. If you find a bug, or an edge case where an exploit fails to succeed against a vulnerable target, do let us know immediately so said situation can be rectified via the bug tracker (issues thing on this repository), or via email/twitter.
## Recent Changes
### Issue #20: Line 46 Fix (Opened May 31, 2021)
A Python 2/3 compatibility issue was identified in the Joomblah exploit at line 46. The issue involves the `binascii.unhexlify()` function returning bytes objects in Python 3 instead of strings, causing a TypeError when attempting string concatenation. The fix requires adding `.decode('utf-8')` to properly handle bytes-to-string conversion:

```python
value = binascii.unhexlify(value).decode('utf-8')
result += value
```

This issue is related to several other reported problems (#17, #19) with the same root cause. A pull request (#22) has been submitted to address this compatibility issue across affected scripts.
## Changes
There is no changelogs here, as that would be too much effort, just git commits. Exploits may be updated regularly for greater stability, reliability or stealthiness, so check them for updates regularly.