Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Is CVE-2023-22515 also exploitable via server-info.action?

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 10, 2023

Rapid7 mentions in their blog post that they exploited the vulnerability CVE-2023-22515 with the endpoint /server-info.action which isn't mentioned in the advisory. Also if it is the case, that this endpoint allows also the creation of an admin account, the workaround won't work.

Can Atlassian confirm this and update the advisory with the additional IoC?

2 answers

1 vote
Tim Eddelbüttel
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 10, 2023

I'll asked this as well in the ticket:

0 votes
Darren DeHaven
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Oct 26, 2023 • edited

Reading the exploit, it appears the workaround doesn't prevent a DoS (triggering a 403 to your system), but does prevent the bad actors from gaining access to your system.


From the exploit:

# It appears the "server-info.action" is used to trigger confluence into a special setup mode. 


# then "server-info.action" is used to add an account

def trigger_vulnerability(self):
status, _ = self.send_request("GET", f"{self.base_url}/server-info.action?bootstrapStatusProvider.applicationConfig.setupComplete=false")
return status == 200

With the workaround, a bad actor can trigger your confluence into a special setup mode (then all your users will get a 403), but the bad actor will be blocked from adding an admin account.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events