# CVE-2022-28771: Missing authorization in SAP Business One License service API

> An unauthenticated attacker can send malicious HTTP requests to the SAP Business One License service API, causing a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rpq2-3p69-p45w

## What is CVE-2022-28771?

CVE-2022-28771 is a high-severity missing authorization vulnerability in SAP Business One License service API, published on 12 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Due to missing authentication check, SAP Business one License service API - version 10.0 allows an unauthenticated attacker to send malicious http requests over the network. On successful exploitation, an attacker can break the whole application making it inaccessible.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 1 product.


Products: Sap Business One License Service Api.

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

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

## Is CVE-2022-28771 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28771 is a high-severity missing authorization vulnerability in SAP Business One License service API, published on 12 Jul 2022. 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-2022-28771 in the wild and no public exploit code.

Affected product: SAP Business One License service API. 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-28771/ (Markdown: https://insights.sbomify.com/CVE-2022-28771/index.md)
```

## Sources

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

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