1-minute read
What a defender needs to know
Atlassian’s CVE record names eight affected customer-managed products: Bitbucket, Confluence, Jira Service Management, Jira Software, Bamboo, Crowd, Crucible and Fisheye. An unauthenticated attacker who knows a file’s specific name and path can read it inside the application web root. Rapid7 describes a researcher demonstration in which a Crowd configuration file, WEB-INF/classes/crowd.properties, exposed credentials; with network access to Crowd, the researchers used them to create a Jira administrator. Crowd IP allowlisting can block that follow-on route. Atlassian Cloud products are already patched.
Inventory each Data Center or server installation and compare its running version with the first fixed release for its product and branch in the full article. Upgrade affected systems; where an update must wait, restrict external access. Review application access logs with request lines decoded up to twice for .. next to /, \ or ::. Investigate matches for configuration-file access and associated authentication or administrator changes. If protected files were read, contain the system and rotate exposed secrets. After updating, verify the running build and review earlier access logs separately: a fixed build protects the current request path, while historical credential use needs its own investigation.