CVE-2022-35168
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 · uneditedDue to improper input sanitization of XML input in SAP Business One - version 10.0, an attacker can perform a denial-of-service attack rendering the system temporarily inoperative.
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 · moderate confidenceImproper input sanitization in SAP Business One version 10.0 allows attackers to send specially crafted XML input that consumes excessive server resources, causing denial of service. This is likely an XML bomb or entity expansion attack where malicious XML payloads cause the parser to allocate vast amounts of memory or CPU.
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= 10.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed SAP Business One versionAccess SAP Business One administration console or check system information panel. Common paths: Help > About in client, or check the SBO Central or License Manager. Alternatively, query the version through SAP B1 server connection settings.Affected if The installed version is exactly 10.0 (version 10.0, no patches or updates applied)
-
Locate XML input endpoints and import functionsReview SAP Business One configuration for features that accept XML input. Common areas: Data Import Wizard (Administration > Import > Data Import), Web Services (SOAP/XML endpoints), REST API endpoints, and any custom integration points using XML.Affected if XML input is accepted through any SAP Business One import or API feature without validation
-
Inspect XML parser configuration for entity expansion limitsCheck SAP Business One server configuration files (typically in the SBO_SP_xx or license server directories) and any XML processing service settings. Look for parser configuration that controls entity expansion, DTD processing, or external entity handling.Affected if XML parser has no limits configured on entity expansion, allows DTD processing, or permits external entities
-
Review XML processing logs for resource consumption patternsExamine SAP Business One logs (typically in the log directory under the SAP Business One installation) for patterns indicating XML parser resource exhaustion: sudden memory spikes, repeated XML parsing failures, or timeout errors during XML operations.Affected if Logs show excessive memory usage or CPU spikes correlated with XML import or API operations, or frequent parser timeout errors
You are affected if you run SAP Business One version 10.0 AND accept XML input through any import or API feature without XML parser hardening against entity expansion attacks.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict XML input validation, disable XML external entities and DTD processing in XML parsers, and consider deploying XML firewall or input validation layer to filter malicious XML payloads before they reach the application.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35168 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-35168 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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