# CVE-2022-28875: Denial-of-Service (DoS) Vulnerability

> Attackers can remotely crash the scanning engine in F-Secure and WithSecure endpoint protection products by exploiting a vulnerability in the aemobile component.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **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:** 25 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-mpcq-pqg7-jfv6

## What is CVE-2022-28875?

CVE-2022-28875 is a medium-severity denial of service vulnerability in All F-Secure & WithSecure endpoint protection products for Windows and Mac. F-Secure Linux Security (32-bit).  F-Secure Linux Security (64-bit).  F-Secure Atlant. WithSecure Cloud Protection for Salesforce & WithSecure Collaboration Protection, published on 25 May 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A Denial-of-Service (DoS) vulnerability was discovered in F-Secure Atlant and in certain WithSecure products whereby the scanning the aemobile component can crash the scanning engine. The exploit can be triggered remotely by an attacker.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2022-28875?

It affects 7 products.


Products: F-Secure Atlant, F-Secure Cloud Protection for Salesforce, F-Secure Elements Collaboration Protection, F-Secure Elements Endpoint Detection and Response, F-Secure Elements Endpoint Protection, F-Secure Internet Gatekeeper, F-Secure Linux Security.

## How do I fix CVE-2022-28875?

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

## Is CVE-2022-28875 being exploited?

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

## Other vulnerabilities in All F-Secure & WithSecure endpoint protection products for Windows and Mac. F-Secure Linux Security (32-bit).  F-Secure Linux Security (64-bit).  F-Secure Atlant. WithSecure Cloud Protection for Salesforce & WithSecure Collaboration Protection

- [CVE-2023-43766](https://insights.sbomify.com/CVE-2023-43766/): Privilege escalation in n/a (high 7.8)
- [CVE-2023-49322](https://insights.sbomify.com/CVE-2023-49322/): Denial of service in n/a (high 7.5)
- [CVE-2023-43760](https://insights.sbomify.com/CVE-2023-43760/): Denial of service in n/a (high 7.5)
- [CVE-2023-43761](https://insights.sbomify.com/CVE-2023-43761/): Denial of service in n/a (high 7.5)
- [CVE-2023-43765](https://insights.sbomify.com/CVE-2023-43765/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28875 and fix it if it is affected.

What it is: CVE-2022-28875 is a medium-severity denial of service vulnerability in All F-Secure & WithSecure endpoint protection products for Windows and Mac. F-Secure Linux Security (32-bit).  F-Secure Linux Security (64-bit).  F-Secure Atlant. WithSecure Cloud Protection for Salesforce & WithSecure Collaboration Protection, published on 25 May 2022. 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-2022-28875 in the wild and no public exploit code.

Affected product: All F-Secure & WithSecure endpoint protection products for Windows and Mac. F-Secure Linux Security (32-bit).  F-Secure Linux Security (64-bit).  F-Secure Atlant. WithSecure Cloud Protection for Salesforce & WithSecure Collaboration Protection. 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-2022-28875/ (Markdown: https://insights.sbomify.com/CVE-2022-28875/index.md)
```

## Sources

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

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