[et_pb_section fb_built=\"1\" _builder_version=\"4.9.4\" _module_preset=\"default\" background_color=\"#2E353D\" custom_padding=\"||0px|||\"][et_pb_row _builder_version=\"4.9.4\" _module_preset=\"default\"][et_pb_column type=\"4_4\" _builder_version=\"4.9.4\" _module_preset=\"default\"][et_pb_text _builder_version=\"4.9.4\" _module_preset=\"cc5ac6f4-ebbd-4b3f-bc92-4dfc1f15fe2c\" hover_enabled=\"0\" sticky_enabled=\"0\"]<\/p>\n
<\/span> Rather than directly attacking cryptography, attackers steal keys, execute man-in-the-middle attacks or steal clear text data of the server while in transit or from the user\u2019s client e.g. browser. A manual attack is generally required.<\/span><\/p>\n <\/span><\/p>\n Inside a Bitbucket application, an administrator can integrate an Elasticsearch-Server. The password is only displayed obfuscated. It is therefore not possible to simply read the password for an already configured server. If an attacker changes the URL of the configured Elasticsearch-Server to his own HTTP server and does not change the password, the password will be sent to the newly configured server address inside a Basic-Auth Header.<\/p>\n To comprehend the vulnerability the following menu can be used: \/rest\/search-admin\/latest\/test-connection<\/p>\n [\/et_pb_text][et_pb_text _builder_version=\"4.9.4\" _module_preset=\"cc5ac6f4-ebbd-4b3f-bc92-4dfc1f15fe2c\" hover_enabled=\"0\" sticky_enabled=\"0\"]<\/p>\n When a new server is configured, user should be required to specify a new password.<\/span><\/p>\n
Advisory ID<\/strong>: usd-2019-0017<\/span>
CVE Number<\/strong>: N\/A<\/span>
Affected Product<\/strong>: Bitbucket<\/span>
Affected Version<\/strong>: v5.10.1<\/span>
Vulnerability Type<\/strong>: Sensitive Data Exposure\/Credentials Disclosure<\/span>
Security Risk<\/strong>: Low<\/span>
Vendor URL<\/strong>: <\/span>https:\/\/www.atlassian.com<\/a>
Vendor Status<\/strong>: Not fixed<\/span><\/p>\n<\/h3>\n
Description<\/h3>\n
Proof of Concept (PoC)<\/h3>\n
Fix<\/h3>\n
<\/h3>\n
Timeline<\/h3>\n