# CVE-2021-41792: Server-side request forgery in n/a

> Attackers can trigger blind server-side requests via crafted HTML files in Alfresco Content Services, potentially bypassing network restrictions.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Oct 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4p6q-fx36-35xg

## What is CVE-2021-41792?

CVE-2021-41792 is a medium-severity server-side request forgery vulnerability in n/a, published on 21 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Hyland org.alfresco:alfresco-content-services through 6.2.2.18 and org.alfresco:alfresco-transform-services through 1.3. A crafted HTML file, once uploaded, could trigger an unexpected request by the transformation engine. The response to the request is not available to the attacker, i.e., this is blind SSRF.

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

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

It affects 2 products.


Products: Alfresco Alfresco Content Services, Alfresco Alfresco Transform Services.

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

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

## Is CVE-2021-41792 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41790](https://insights.sbomify.com/CVE-2021-41790/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41792 is a medium-severity server-side request forgery vulnerability in n/a, published on 21 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41792 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-2021-41792/ (Markdown: https://insights.sbomify.com/CVE-2021-41792/index.md)
```

## Sources

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

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