In April 2010, a cross-site scripting vulnerability in Atlassian’s Jira issue-tracking software was used to compromise two Apache Software Foundation servers. The incident exposed Jira’s password database, which contained unsalted password hashes vulnerable to rainbow-table attacks, dictionary lookups, and password-cracking tools. Apache advised affected users to change their passwords after the breach was discovered.
Atlassian also acknowledged that it had been targeted in the same attack. The company disclosed that a legacy database containing passwords stored in plain text had been compromised, turning a software vulnerability into a broader credential-security failure. The source does not identify a named executive, attacker, financial loss, or subsequent court or regulatory action, but the episode demonstrated the consequences of retaining weakly protected credentials in a widely deployed commercial development platform.