LiveActive security incident?Get immediate response
CVE Record

CVE-2017-16028: react-native-meteor-oauth is a library for Oauth2 login to a Meteor server in React Native.

react-native-meteor-oauth is a library for Oauth2 login to a Meteor server in React Native. The oauth Random Token is generated using a non-cryptographically strong RNG (Math.random()).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE concerns weak randomness in a React Native OAuth helper for Meteor. The library generated an OAuth random token using Math.random(), which is not suitable for security tokens. Business risk depends on whether the package is present in a production mobile login flow.

Executive priority

Prioritize discovery first. This is authentication-adjacent, but severity is unspecified and exploitation is not evidenced in the supplied sources. Escalate remediation if the library is found in active production mobile login flows.

Technical view

react-native-meteor-oauth uses a non-cryptographically strong random number generator for an OAuth random token. The source bundle maps this to CWE-330 and lists all versions of the node module as affected. No CVSS score, fixed version, or vendor mitigation is provided in the supplied sources.

Likely exposure

Exposure is likely limited to React Native applications that use the react-native-meteor-oauth node module for OAuth2 login to a Meteor server. The supplied affected data says all versions are affected, but no package prevalence or deployment context is provided.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not marked as CISA KEV. The practical impact depends on how the OAuth token is used by the application and whether weak token unpredictability can affect authentication integrity.

Researcher notes

Evidence is narrow: the CVE description, affected package statement, CWE-330 classification, and a source reference to token generation. The bundle does not provide impact scoring, exploitability details, a patched release, or proof of exploitation.

Mitigation direction

  • Inventory React Native apps for react-native-meteor-oauth usage.
  • Check project and advisory guidance for any fixed version or replacement guidance.
  • Treat all listed versions as affected until authoritative guidance says otherwise.
  • Remove or isolate affected OAuth flows if no supported fix exists.
  • Rotate relevant sessions or OAuth state after remediation, where operationally appropriate.

Validation and detection

  • Review dependency manifests for react-native-meteor-oauth.
  • Confirm whether the package is used in production authentication flows.
  • Inspect token generation paths for Math.random() or similar weak randomness.
  • Compare installed versions against vendor or advisory guidance.
  • Validate login behavior after any replacement or remediation.
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.

cwe · low confidence lookup

CWE-330: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-16028 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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HackerOnereact-native-meteor-oauth node moduleAll versionsListed
Weakness

CWE details

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

CWE-330 · source CWE mapping

Use of Insufficiently Random Values

Use of Insufficiently Random Values represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.