CVE-2024-11831: Npm-serialize-javascript: cross-site scripting (xss) in serialize-javascript
A flaw was found in npm-serialize-javascript. The vulnerability occurs because the serialize-javascript module does not properly sanitize certain inputs, such as regex or other JavaScript object types, allowing an attacker to inject malicious code. This code could be executed when deserialized by a web browser, causing Cross-site scripting (XSS) attacks. This issue is critical in environments where serialized data is sent to web clients, potentially compromising the security of the website or web application using this package.
Security readout for executives and security teams
Plain-English summary
This is a cross-site scripting flaw in serialize-javascript. If an application sends unsafe serialized data to a browser, attacker-controlled JavaScript-like content could execute in a user’s session. Business impact is mainly user trust, session exposure, and data integrity, not server takeover.
Executive priority
Treat as a medium-priority application security issue. Accelerate remediation for customer-facing sites and admin consoles, especially where lower-privileged users can create content viewed by others. No source evidence indicates active exploitation, but XSS can still create meaningful account and data exposure.
Technical view
CVE-2024-11831 is CWE-79 in serialize-javascript, reported against version 6.0 and bundled in several Red Hat products. The flaw involves insufficient sanitization of inputs such as regex or JavaScript object types before browser use. CVSS 3.1 is 5.4: network reachable, low complexity, low privileges, user interaction required, changed scope.
Likely exposure
Exposure is most likely in web applications or management consoles that use serialize-javascript and send serialized, attacker-influenced data to clients. The bundle lists serialize-javascript 6.0 and specific Red Hat ACS, Ceph, RHEL dotnet8.0, and ODF package builds as affected.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires a path where a low-privileged attacker can influence serialized content and a user later opens a browser view that deserializes or executes it.
Researcher notes
Key uncertainty is fix detail: the bundle lists affected versions and Red Hat errata, but not exact fixed serialize-javascript or packaged versions. Validate reachability by data flow, not package presence alone, because risk depends on serialized attacker-controlled values reaching browser execution contexts.
Mitigation direction
Check upstream serialize-javascript and Red Hat advisories for fixed versions.
Prioritize updates for internet-facing or shared administrative web consoles.
Identify and reduce browser exposure of attacker-controlled serialized data.
Use safe output encoding and avoid executing serialized content in clients.
Apply relevant Red Hat errata where affected packaged products are deployed.
Validation and detection
Inventory dependencies for serialize-javascript version 6.0 or vulnerable packaged builds.
Search applications for server-generated serialized JavaScript embedded in browser pages.
Map affected Red Hat package names to deployed ACS, Ceph, RHEL, and ODF systems.
Confirm whether serialized fields can be influenced by low-privileged users.
Verify remediation against vendor advisory versions, not inferred package names.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.