LiveActive security incident?Get immediate response
CVE Record

CVE-2017-1000048: the web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a...

the web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE affects applications or frameworks that use old versions of the Node.js qs module. A crafted request can crash the web framework, causing denial of service. The public record names fixed qs branch versions but provides no CVSS score, CWE, or confirmed active exploitation.

Executive priority

Handle in normal vulnerability remediation cycles, with faster action for internet-facing Node.js services. The business risk is service disruption, not data theft based on the provided sources.

Technical view

CVE-2017-1000048 is a denial-of-service flaw in qs before 6.3.2, 6.2.3, 6.1.2, and 6.0.4 as consumed by web frameworks. The source bundle says malicious requests can trigger a framework crash. A Red Hat advisory is referenced, but affected product details are not enumerated in the provided CVE data.

Likely exposure

Exposure is most likely in Node.js web applications or framework dependencies that include qs versions older than the fixed branch releases. The provided affected-product metadata is incomplete, so asset impact requires dependency inventory review.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked as CISA KEV. Treat this as a remotely triggerable availability risk where untrusted HTTP requests reach vulnerable qs parsing paths.

Researcher notes

Evidence is thin: no CVSS vector, CWE, detailed affected-product list, or exploitation confirmation is provided. Avoid assuming all qs consumers are exploitable; validate whether vulnerable parsing code is reachable from untrusted requests.

Mitigation direction

  • Upgrade qs to a fixed release for the applicable branch.
  • Review vendor guidance for frameworks bundling or pinning qs.
  • Apply relevant Red Hat advisory updates where applicable.
  • Prioritize internet-facing services that parse untrusted query strings.
  • Restart or redeploy services after dependency updates.

Validation and detection

  • Search dependency manifests and lockfiles for qs versions.
  • Check transitive dependencies from web frameworks and middleware.
  • Confirm deployed builds use fixed qs versions.
  • Review uptime logs for unexplained framework crashes.
  • Verify Red Hat package status where RHSA-2017:2672 applies.
Prepared
Confidence
medium
Sources
4

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.

cve · low confidence lookup

CVE-2017-1000048 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.