# CVE-2019-13347: Auth bypass in n/a

> Attackers can reactivate disabled accounts by browsing the site if specific SAML plugin settings are enabled, bypassing account deactivation controls.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Dec 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pq6q-vhr6-vqvj

## What is CVE-2019-13347?

CVE-2019-13347 is a high-severity authentication bypass vulnerability in n/a, published on 13 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2019-13347?

It affects 1 product.


Products: Atlassian Saml Single Sign On.

## How do I fix CVE-2019-13347?

No fix has been published for CVE-2019-13347 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-13347 being exploited?

There is no known exploitation of CVE-2019-13347 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-37843](https://insights.sbomify.com/CVE-2021-37843/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-13347 and fix it if it is affected.

What it is: CVE-2019-13347 is a high-severity authentication bypass vulnerability in n/a, published on 13 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13347 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-13347/ (Markdown: https://insights.sbomify.com/CVE-2019-13347/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-13347
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-13347
- OSV: https://osv.dev/vulnerability/CVE-2019-13347

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-13347/
Summaries are generated and may contain mistakes; the official description above is the record.