Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Apache Tomcat AJP RCE Vulnerability (Ghostcat) disable AJP service

Our 3rd party ASV is detecting an incident against our self hosted Bitbucket Server instance: 

Apache Tomcat AJP RCE Vulnerability (Ghostcat)

According to an article I found, the AJP connector service can be disabled by commenting out or removing the appropriate line from the $CATALINA_HOME/conf/server.xml file and restarting Tomcat.

Based on my understanding, Tomcat is embedded as part of Bitbucket Server and not a seperate install so how can this service be disabled?

1 answer

1 accepted

3 votes
Answer accepted
Daniel Eads Atlassian Team May 28, 2021

Hi @grantmcinnes ,

I see you've listed that you're on Bitbucket Server 7.6 in your question information. Given that, can you double-check your ASV for a specific CVE it is checking against and what its detection criteria is?

CVE-2020-1938 (Ghostcat) was mitigated in Tomcat 9.0.31, which we incorporated into Bitbucket Server starting in version 7.1.0. Bitbucket Server versions in the 7.6 line are not susceptible to CVE-2020-1938.

If by chance you are on an older version, you can look in bitbucket.properties for this string:

connector-protocol=AJP/1.3

Bitbucket Server's containerized setup is a bit different than most applications running in Tomcat - for example in Jira, you would set an AJP connector up in the server.xml file. In Bitbucket Server, configuration items like this are in the bitbucket.properties file

It is very uncommon to have AJP enabled with Bitbucket Server, although it is possible. I would go through those two steps to see if this is something you need to modify:

  1. Bitbucket Server 7.6 has a mitigated Tomcat version - no need for concern on this version or newer
  2. If you're on Bitbucket Server older than version 7.1.0, check the bitbucket.properties file for an enabled AJP connector

Let me know what you find and we'll get you sorted if there's something to change!

Cheers,
Daniel | Atlassian Support

@Daniel Eads Thanks for the reply. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
7.6
TAGS
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

345 views 2 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you