Xerces C\+\+Application · Apache
CVE-2023-37536
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 · uneditedAn integer overflow in xerces-c++ 3.2.3 in BigFix Platform allows remote attackers to cause out-of-bound access via HTTP request.
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 confidenceInteger overflow vulnerability in xerces-c++ library version 3.2.3 used by BigFix Platform allows remote attackers to trigger out-of-bounds memory access via specially crafted HTTP requests, potentially leading to memory corruption or arbitrary code execution.
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
Xerces C\+\+Application
= 3.2.3
FedoraOperating system
= 37>= 9.0.0, < 9.5.23>= 10.0.0, < 10.0.10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 BigFix Platform versionLocate the BigFix installation directory and check the version information file, or run the BigFix client version command (typically 'bfclient -version' or check the BES Client service properties)Affected if Version is 9.0.0 through 9.5.22, or 10.0.0 through 10.0.9 (these ranges indicate the vulnerable xerces-c++ library is bundled)
-
Locate and verify xerces-c++ library versionSearch for 'xerces-c_3.dll' or 'libxerces-c.so' within the BigFix installation directory, then use a binary version checker or strings command to extract the embedded version stringAffected if The library file reports version 3.2.3 exactly, indicating the vulnerable version is present
-
Confirm HTTP listeners are activeCheck BigFix configuration for enabled HTTP/HTTPS listener services (typically ports 52311, 52314, or custom ports), using 'netstat' or 'ss' to list active listening portsAffected if BigFix is listening for HTTP connections, as the vulnerability is triggered via specially crafted HTTP requests to the BigFix server component that uses xerces-c++ for XML parsing
Your environment is affected if BigFix Platform versions 9.0.0-9.5.22 or 10.0.0-10.0.9 are running with xerces-c++ version 3.2.3 and the platform has HTTP listeners enabled for client communications.
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 · scoped9.5.2310.0.10
Update BigFix Platform to a version that includes a patched xerces-c++ library (version 3.2.4 or later), or apply vendor-supplied patches; validate the fix in a non-production environment before deployment.
Xerces C++ 3.2.4+ (or 3.2.5); BigFix 9.5.23; BigFix 10.0.10
- For Xerces C++: Upgrade to version 3.2.4 or later (e.g., 3.2.5) from the official Apache Xerces-C++ project
- For Fedora 37: Apply the Fedora security update for xerces-c (run: dnf update xerces-c)
- For BigFix Platform 9.x: Upgrade to version 9.5.23 or later
- For BigFix Platform 10.x: Upgrade to version 10.0.10 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Xerces C\+\+
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37536 — 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-2023-37536 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