dbcve.org
Business One License Service ApiApplication · Sap

CVE-2022-28771

HIGH · 7.5 CVSS v3.1 Published 2022-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Missing authentication check in SAP Business One License service API version 10.0 allows unauthenticated remote attackers to send malicious HTTP requests to the service. Successful exploitation can render the entire application inaccessible by breaking the license service functionality.

MitigationImplement proper authentication and authorization controls on the License service API endpoints, or apply vendor-supplied security patches for version 10.0. Consider network segmentation to limit exposure of the license service to untrusted networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Business One License Service ApiApplication
Affected:= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SAP Business One License Service API version
    Locate the SAP Business One License Service API installation directory and check the version information file, or use the SAP Business One version information tool (About > System Information) to identify the License Service component version
    Affected if The installed License Service API version is exactly 10.0 (or falls within the 10.0 release line)
  2. Determine if License service API is network-accessible
    Identify the port used by the SAP Business One License Service (typically ports 30000-30010 range) and test external network connectivity to those ports using telnet, netcat, or a simple TCP connection test from an untrusted network segment
    Affected if The License service API port is reachable from untrusted networks without firewall filtering
  3. Check License service API endpoint accessibility
    Send an unauthenticated HTTP request to the License service API endpoint (such as GET / or a known API probe request) using curl or similar tool to verify if the service responds without requiring authentication credentials
    Affected if The License service API responds to HTTP requests without rejecting them due to missing authentication credentials
  4. Inspect License service API configuration files
    Examine the SAP Business One License Service configuration files in the installation directory for authentication settings, looking for parameters related to authentication enforcement, security mode, or access control lists
    Affected if Authentication enforcement is disabled, set to optional, or missing from the License service API configuration

The environment is affected if SAP Business One License Service API version 10.0 is installed AND the License service API is accessible without authentication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization controls on the License service API endpoints, or apply vendor-supplied security patches for version 10.0. Consider network segmentation to limit exposure of the license service to untrusted networks.

Fix this in Business One License Service Api Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28771 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28771 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data