First published: Fri Dec 13 2019(Updated: )
An issue was discovered in the SAML Single Sign On (SSO) plugin for several Atlassian products affecting versions 3.1.0 through 3.2.2 for Jira and Confluence, versions 2.4.0 through 3.0.3 for Bitbucket, and versions 2.4.0 through 2.5.2 for Bamboo. It allows locally disabled users to reactivate their accounts just by browsing the affected Jira/Confluence/Bitbucket/Bamboo instance, even when the applicable configuration option of the plugin has been disabled ("Reactivate inactive users"). Exploiting this vulnerability requires an attacker to be authorized by the identity provider and requires that the plugin's configuration option "User Update Method" have the "Update from SAML Attributes" value.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Atlassian SAML Single Sign-On | >=2.4.0<=3.0.3 | |
Atlassian SAML Single Sign-On | >=2.4.0<=3.0.3 | |
Atlassian SAML Single Sign-On | >=3.1.0<=3.2.2 | |
Atlassian SAML Single Sign-On | >=3.1.0<=3.2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-13347 is classified as a medium severity vulnerability.
To fix CVE-2019-13347, upgrade the SAML Single Sign On plugin to versions 3.2.2 or later for Jira and Confluence, and to versions 3.0.3 or later for Bitbucket and Bamboo.
CVE-2019-13347 affects Jira, Confluence, Bitbucket, and Bamboo versions mentioned in the description.
CVE-2019-13347 allows locally disabled users to reactivate their accounts without proper authorization.
CVE-2019-13347 was disclosed on July 11, 2019.