LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19729: An issue was discovered in the BSON ObjectID (aka bson-objectid) package 1.3.0 for Node.js.

An issue was discovered in the BSON ObjectID (aka bson-objectid) package 1.3.0 for Node.js. ObjectID() allows an attacker to generate a malformed objectid by inserting an additional property to the user-input, because bson-objectid will return early if it detects _bsontype==ObjectID in the user-input object. As a result, objects in arbitrary forms can bypass formatting if they have a valid bsontype.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-19729 affects the Node.js bson-objectid package version 1.3.0. The package may accept a user-supplied object as if it were a valid ObjectID when it contains a BSON type marker, allowing malformed identifiers to bypass expected formatting checks.

Executive priority

Treat this as a targeted dependency and validation review, not an emergency unless the package protects sensitive authorization or lookup paths. Prioritize internet-facing Node.js services first.

Technical view

ObjectID() in bson-objectid 1.3.0 can return early when user input appears to have _bsontype equal to ObjectID. This can let arbitrary object shapes bypass ObjectID formatting validation. The sources do not provide CVSS, CWE, affected CPEs, fixed version, or vendor remediation details.

Likely exposure

Exposure is most likely in Node.js applications that directly or transitively depend on bson-objectid 1.3.0 and construct ObjectIDs from untrusted user-controlled objects.

Exploitation context

The provided sources do not report active exploitation, and the CVE is not listed as KEV. Business impact depends on how applications use ObjectIDs for authorization, lookups, routing, or validation decisions.

Researcher notes

Evidence is limited to the CVE description and upstream references. No public CVSS, CWE, patch version, or exploit-in-the-wild signal is included in the provided bundle, so impact must be validated in application context.

Mitigation direction

  • Inventory direct and transitive use of bson-objectid 1.3.0.
  • Check the GitHub issue and npm package page for current vendor guidance.
  • Avoid trusting user-supplied object type markers at application boundaries.
  • Add application validation that rejects malformed ObjectID inputs before business logic.
  • Assess whether replacing the package is safer if vendor guidance is absent.

Validation and detection

  • Review dependency manifests and lockfiles for bson-objectid 1.3.0.
  • Identify code paths that construct ObjectIDs from request bodies or parameters.
  • Confirm malformed ObjectID-like objects are rejected before database or authorization logic.
  • Add regression tests covering object-shaped input, not only string IDs.
  • Track remediation status against the CVE record and upstream package references.
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-2019-19729 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.