CVE-2023-28103
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 · uneditedmatrix-react-sdk is a Matrix chat protocol SDK for React Javascript. In certain configurations, data sent by remote servers containing special strings in key locations could cause modifications of the `Object.prototype`, disrupting matrix-react-sdk functionality, causing denial of service and potentially affecting program logic. This is fixed in matrix-react-sdk 3.69.0 and users are advised to upgrade. There are no known workarounds for this vulnerability. Note this advisory is distinct from GHSA-2x9c-qwgf-94xr which refers to a similar issue.
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 confidencematrix-react-sdk versions before 3.69.0 are vulnerable to prototype pollution. When the SDK processes data received from remote Matrix servers, specially crafted strings in key locations can modify Object.prototype, disrupting SDK functionality and potentially affecting application logic. This is a prototype pollution vulnerability specific to how the SDK handles server-supplied data.
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< 3.69.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
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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.
-
Locate matrix-react-sdk installationCheck your project's package.json dependencies section, or run 'npm list matrix-react-sdk' to see the installed versionAffected if matrix-react-sdk is not present in dependencies
-
Identify the installed versionRead the version number from package.json or the npm list output, typically found in node_modules/matrix-react-sdk/package.json under the 'version' fieldAffected if The version string is lower than 3.69.0 (for example: 3.68.0, 3.60.0, etc.)
-
Verify the application uses Matrix server dataConfirm that your application initializes and uses the Matrix React SDK to connect to Matrix servers and process room data, events, or user profilesAffected if The application processes data received from remote Matrix servers (this is the SDK's primary function)
You are affected if your installed matrix-react-sdk version is below 3.69.0 and your application uses the SDK to process data from Matrix servers.
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 · scoped3.69.0
Upgrade matrix-react-sdk to version 3.69.0 or later. There are no workarounds; the upgrade is mandatory to remediate this vulnerability.
matrix-react-sdk version 3.69.0 or later
- 1. Identify the current version of matrix-react-sdk in use by checking package.json or package-lock.json
- 2. Upgrade matrix-react-sdk to version 3.69.0 or later using your package manager (e.g., npm install matrix-react-sdk@^3.69.0 or yarn upgrade matrix-react-sdk@^3.69.0)
- 3. Rebuild and test the application to verify the upgrade does not introduce regressions
- 4. Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28103 — 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-28103 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