# CVE-2023-36627: FlashBlade Snapshot Scheduler

> Administrative users can disrupt snapshot schedules by configuring specific timezones, causing denial of service for backup operations.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/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:** 2 Oct 2023
- **Updated:** 23 Sep 2024
- **Also known as:** GHSA-v8xg-wm26-8m5w

## What is CVE-2023-36627?

CVE-2023-36627 is a high-severity vulnerability in Pure Storage FlashBlade Purity, published on 2 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw exists in FlashBlade Purity whereby a user with access to an administrative account on a FlashBlade that is configured with timezone-dependent snapshot schedules can configure a timezone to prevent the schedule from functioning properly.

## Which versions are affected by CVE-2023-36627?

It affects 1 product.


Products: Purestorage Purity.

## How do I fix CVE-2023-36627?

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

## Is CVE-2023-36627 being exploited?

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

## Other vulnerabilities in Pure Storage FlashBlade Purity

- [CVE-2023-31042](https://insights.sbomify.com/CVE-2023-31042/): FlashBlade Object Store Protocol (high 7.7)
- [CVE-2023-28372](https://insights.sbomify.com/CVE-2023-28372/): FlashBlade Object Store Privileged Access (medium 6.5)
- [CVE-2017-7352](https://insights.sbomify.com/CVE-2017-7352/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-36627 and fix it if it is affected.

What it is: CVE-2023-36627 is a high-severity vulnerability in Pure Storage FlashBlade Purity, published on 2 Oct 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-36627 in the wild and no public exploit code.

Affected product: Pure Storage FlashBlade Purity. 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-2023-36627/ (Markdown: https://insights.sbomify.com/CVE-2023-36627/index.md)
```

## Sources

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

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