CSV Injection vulnerability identified in the reporting modules.

Issue #285 resolved
created an issue

After performing Twitter OSINT on a user with a specific malicious payload as a username, the resulting CSV and XLSX reports can be created with poisoned data.

Attached is the writeup encrypted with LanMaster53's public key.

Comments (5)

  1. Tim Tomes repo owner

    Hah! I love this. Thanks for sharing. I know there is potential for this in a few places, but I'm not sure I'm going to do anything about it. As security people, I'm hoping people know not to click through warnings like that. FTR, I know this is a terrible answer that would never fly in a production environment. USE AT YOUR OWN RISK! :-)

  2. Tim Tomes repo owner

    Removed broken CAPTCHA answering logic for Google searching. Resolves issue #219. Resolves issue #249.

    Removed the picasa pushpin module due to the API being taken offline. Resolves issue #278.

    Added the threatminer subdomain search module.

    Added the findsubdomain module.

    Remediated a CSV injection vulnerability in the csv reporting module. Resolves Issue #285.

    Added several IANA PEN modules.

    → <<cset 41e96fd58891>>

  3. Log in to comment