Skip to content
Fencer Vulns
high 7.5

CVE-2021-33623 json

Uncontrolled Resource Consumption in trim-newlines

published 2021-05-28 5 y ago modified 2026-09-10 1 mo ago also GHSA-7p7h-4mm5-852v , EUVD-2021-1281

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.9%
EPSS 2.9% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method.

Patch / fix

  • npm trim-newlines 3.0.1, 4.0.1
  • trim-newlines_project trim-newlines 3.0.1, 4.0.1
  • node-trim-newlines Debian 14, Debian 13, Debian 12 3.0.0+~3.0.0-1

debian advisories DEBIAN-CVE-2021-33623

  • node-trim-newlines Ubuntu 18.04 LTS 1.0.0-1ubuntu0.18.04.1
  • node-trim-newlines Ubuntu 20.04 LTS 1.0.0-1ubuntu0.20.04.1

ubuntu advisories UBUNTU-CVE-2021-33623

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • ovirt-web-ui rhev manager 4.4 1.9.0-1.el8ev
  • ovirt-dependencies rhev manager 4.4 4.5.2-1.el8ev
  • apache-commons-compress rhev manager 4.4 1.21-1.2.el8ev
  • apache-commons-compress-javadoc rhev manager 4.4 1.21-1.2.el8ev

red hat advisories RHSA-2022:5555

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2021-33623 updated cvss 7.5

nodejs-trim-newlines: ReDoS in .end() method

  • Red Hat OpenShift Service Mesh 2.0 servicemesh-grafana, servicemesh-grafana-prometheus
    affected: no fix available
  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/grc-ui-rhel8, rhacm2/console-rhel8, rhacm2/search-ui-rhel8, rhacm2/console-ui-rhel8, rhacm2/console-api-rhel8, rhacm2/mcm-topology-rhel8, +2 more
    affected: no fix available “Fix deferred”
  • Red Hat Ansible Automation Platform 1.2 trim-newlines
    affected: no fix available
  • Red Hat OpenShift Container Platform 4 openshift4/ose-grafana Red Hat Virtualization 4 ovirt-engine-ui-extensions
    affected: no fix available “Fix deferred”
  • Red Hat Cluster Observability Operator 1.5 cluster-observability-operator/distributed-tracing-console-plugin-pf4-rhel9 1782840519
    fixed: vendor fix RHSA-2026:34342
  • Red Hat RHEL-8-RHEV-S-4.4 - Red Hat Virtualization Engine 4.4 ovirt-web-ui 1.9.0-1.el8ev
    fixed: vendor fix RHSA-2022:5555
  • Red Hat Cluster Observability Operator 1.5 cluster-observability-operator/perses-rhel9 1782839109, cluster-observability-operator/thanos-rhel9 1782840280, cluster-observability-operator/korrel8r-rhel9 1782839157, cluster-observability-operator/prometheus-rhel9 1782840780, cluster-observability-operator/alertmanager-rhel9 1782840761, cluster-observability-operator/perses-rhel9-operator 1782839191, +18 more Red Hat RHEL-8-RHEV-S-4.4 - Red Hat Virtualization Engine 4.4 rhvm 4.5.1.2-0.11.el8ev, ovirt-engine-dwh 4.5.3-1.el8ev, ovirt-engine 4.5.1.2-0.11.el8ev, postgresql-jdbc 42.2.14-1.el8ev, rhvm-branding-rhv 4.5.0-1.el8ev, ovirt-dependencies 4.5.2-1.el8ev, +26 more
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.93% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
npm trim-newlines
<3.0.1
>=4.0.0, <4.0.1
3.0.1
4.0.1

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.