View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009503 | Kali Linux | Kali Package Bug | public | 2026-01-15 01:43 | 2026-01-17 13:01 |
| Reporter | erikdervishi | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 0009503: Steghide 0.5.1-15 crashes (stack smashing detected) on long paths, causing sensitive data leak via core dump | ||||
| Description | Package: steghide Version: 0.5.1-15 Architecture: amd64 Maintainer: Debian Security Team Scenario: I installed steghide from the official Kali Linux repositories. I attempted to embed data into a valid WAV file located in a directory path that, combined with the filename, exceeds 200 bytes in length. Upon execution, the application crashes immediately. Analysis: The crash is caused by a stack-based buffer overflow in src/Embedder.cc. The application uses an unsafe sprintf call to write the status message into a fixed-size buffer (char buf[200]) without bounds checking. The system's Stack Smashing Protector (SSP) correctly detects this violation and terminates the process to prevent arbitrary code execution. Error Message: Impact Analysis:
System Information: Proposed Fix: The original upstream project is inactive. I have submitted a patch to the community fork (StegHigh) that replaces the unsafe sprintf with snprintf. Pull Request: https://github.com/StegHigh/steghide/pull/21 Steps to Reproduce:
#!/bin/bash 1. Enable core dumps to verify leakulimit -c unlimited 2. Define long path > 200 bytesLONG_DIR=$(python3 -c "print('A' 200)") 3. Generate valid 50KB WAV file (Header + Silence)Required to bypass initial file format checks and reach the vulnerable codepython3 -c " 4. Create dummy secretecho "secret data" > secret.txt 5. Run Steghide with a specific passwordecho "Launching steghide with password 'MY_SECRET_PASS'..."
3 .Verify the Data Leak: Locate the core dump and search for the password string. Using coredumpctl (systemd default on Kali)coredumpctl dump steghide > crash.dump Result: The strings command outputs MY_SECRET_PASS multiple times, confirming the passphrase leaked to disk. | ||||
|
You know that you should report this to the development team of that software itself? |
|
|
I would normally report this upstream, but the original project on SourceForge is abandoned and unmaintained (last update was in 2005). There is no active upstream development team to report to anymore. Since Kali and Debian continue to ship this package, and this is a reproducible security vulnerability (Stack Buffer Overflow causing Information Disclosure via core dumps), the fix needs to be applied at the distribution packaging level (e.g., via debian/patches). A fix is already available in the community fork "StegHigh" (PR 0000021), which simply replaces the unsafe sprintf with snprintf |
|
|
What about https://github.com/StegHigh/steghide which is (some kind of active), has an issue tracker and allows fixes via pull requests?
Distro patches for upstream issues without notification to upstream by the reporter is probably the last resort which sould be taken. |
|
|
Ah, https://github.com/StegHigh/steghide/pull/21 is what has been meant with "community fork" (which seem actually the official repo and not the fork based on the previous quote) so all good. Correct way probably would be:
|
|
|
Ok, thanks! I have requested the CVE and will update this thread as soon as I get the ID |
|
|
Kali-bugreport can i ask how can i join to your side as a programmer on discord group they advice to come on here |
|
|
Nice, i think this will benefit all Linux distributions if a CVE will get assigned. It seems the Tool is also getting pulled / imported by Kali from Debian: https://pkg.kali.org/pkg/steghide and once it received a fix in Debian it will also automatically land in Kali. |
|
|
And how is if i want to build new tool lets say tool for tracking so where can i post it |
|
|
@Shopyle No idea what you are talking about and i don't care. If you are not a spambot please stop posting completely unrelated stuff like this here in random unrelated issues. |
|
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-01-15 01:43 | erikdervishi | New Issue | |
| 2026-01-16 06:18 | kali-bugreport | Note Added: 0021256 | |
| 2026-01-16 10:27 | erikdervishi | Note Added: 0021259 | |
| 2026-01-16 10:34 | kali-bugreport | Note Added: 0021260 | |
| 2026-01-16 10:40 | kali-bugreport | Note Edited: 0021260 | |
| 2026-01-16 11:06 | kali-bugreport | Note Added: 0021262 | |
| 2026-01-16 12:36 | kali-bugreport | Note Edited: 0021262 | |
| 2026-01-16 16:14 | erikdervishi | Note Added: 0021267 | |
| 2026-01-16 17:18 | Shopyle | Note Added: 0021268 | |
| 2026-01-16 18:03 | kali-bugreport | Note Edited: 0021262 | |
| 2026-01-16 18:06 | kali-bugreport | Note Added: 0021269 | |
| 2026-01-16 18:26 | Shopyle | Note Added: 0021270 | |
| 2026-01-16 19:04 | kali-bugreport | Note Added: 0021271 | |
| 2026-01-16 19:45 | kali-bugreport | Note Edited: 0021271 | |
| 2026-01-17 13:01 | kali-bugreport | Note Edited: 0021271 |