CVE-2022-1700
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 · uneditedImproper Restriction of XML External Entity Reference ('XXE') vulnerability in the Policy Engine of Forcepoint Data Loss Prevention (DLP), which is also leveraged by Forcepoint One Endpoint (F1E), Web Security Content Gateway, Email Security with DLP enabled, and Cloud Security Gateway prior to June 20, 2022. The XML parser in the Policy Engine was found to be improperly configured to support external entities and external DTD (Document Type Definitions), which can lead to an XXE attack. This issue affects: Forcepoint Data Loss Prevention (DLP) versions prior to 8.8.2. Forcepoint One Endpoint (F1E) with Policy Engine versions prior to 8.8.2. Forcepoint Web Security Content Gateway versions prior to 8.5.5. Forcepoint Email Security with DLP enabled versions prior to 8.5.5. Forcepoint Cloud Security Gateway prior to June 20, 2022.
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 confidenceXXE vulnerability in Forcepoint DLP Policy Engine where the XML parser improperly supports external entities and external DTD processing. Attackers can inject malicious XML to read internal files, perform SSRF attacks, or cause denial of service by referencing external entities that may access local resources or trigger unintended network requests.
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< 2022-06-20< 8.8.2< 8.5.5< 8.8.2< 8.5.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Forcepoint productLocate the Forcepoint product installed in your environment. Common installation directories include /opt/forcepoint/ or check system services for Forcepoint-related processes (e.g., dpdl, fwsvr, csg). Review installed software or running services to confirm the specific Forcepoint component.Affected if Any Forcepoint product from the affected list is installed (Cloud Security Gateway, Data Loss Prevention, Email Security, One Endpoint with Policy Engine, or Web Security Content Gateway).
-
Determine product versionCheck the installed version of the identified Forcepoint product. Common methods: check the software GUI About section, run 'dpdl --version' or 'fwsvr --version' from command line if available, or inspect version files in the installation directory (often in /opt/forcepoint/<product>/version or similar).Affected if Version cannot be determined or is below the safe threshold.
-
Compare against affected version rangesMatch your installed version to the affected ranges: Cloud Security Gateway < 2022-06-20, Data Loss Prevention < 8.8.2, Email Security < 8.5.5, One Endpoint With Policy Engine < 8.8.2, Web Security Content Gateway < 8.5.5.Affected if Installed version falls below the specified threshold for your product.
-
Locate XML parser configurationSearch for XML parser or XML processing configuration files within the Forcepoint installation directory. Look for files containing xml, parser, or xxe in the name. Common paths may include /opt/forcepoint/dlp/config/ or similar. Review configuration for settings related to external entity processing.Affected if External entity or external DTD processing is enabled in the XML parser configuration (e.g., feature for external entities is not explicitly disabled).
You are affected if your installed Forcepoint product version is below 8.8.2 (DLP/One Endpoint) or 8.5.5 (Email/Web Security) or predates June 20, 2022 (Cloud Security Gateway) AND the XML parser has external entity/external DTD processing enabled.
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.
dbcve · scoped8.5.58.8.22022-06-20
Update Forcepoint DLP and F1E to version 8.8.2 or later, Web Security/Email Security to 8.5.5 or later, and Cloud Security Gateway to the June 20, 2022 or later patch. Alternatively, configure the XML parser to disable external entity and external DTD processing.
DLP: 8.8.2+ | One Endpoint: 8.8.2+ | Web Security Content Gateway: 8.5.5+ | Email Security: 8.5.5+ | Cloud Security Gateway: 2022-06-20+
- Upgrade Forcepoint Data Loss Prevention (DLP) to version 8.8.2 or later
- Upgrade Forcepoint One Endpoint (F1E) with Policy Engine to version 8.8.2 or later
- Upgrade Forcepoint Web Security Content Gateway to version 8.5.5 or later
- Upgrade Forcepoint Email Security with DLP enabled to version 8.5.5 or later
- Upgrade Forcepoint Cloud Security Gateway to version released on June 20, 2022 or later
- After upgrade, verify the XML parser configuration in Policy Engine no longer supports external entities and external DTDs
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1700 — 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-1700 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