# CVE-2021-27550: Denial of service in n/a

> A divide-by-zero error in Polaris Office allows local attackers to cause a denial of service by tricking users into opening a crafted PDF file.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 23 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-q9cg-7392-75cw

## What is CVE-2021-27550?

CVE-2021-27550 is a medium-severity denial of service vulnerability in n/a, published on 23 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Polaris Office v9.102.66 is affected by a divide-by-zero error in PolarisOffice.exe and EngineDLL.dll that may cause a local denial of service. To exploit the vulnerability, someone must open a crafted PDF file.

Weakness: CWE-369 (Divide By Zero)

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

It affects 1 product.


Products: Polarisoffice Polaris Office.

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

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

## Is CVE-2021-27550 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-34280](https://insights.sbomify.com/CVE-2021-34280/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-27550 is a medium-severity denial of service vulnerability in n/a, published on 23 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-27550 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-27550/ (Markdown: https://insights.sbomify.com/CVE-2021-27550/index.md)
```

## Sources

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

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