LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13146: The field_test gem 0.3.0 for Ruby has unvalidated input.

The field_test gem 0.3.0 for Ruby has unvalidated input. A method call that is expected to return a value from a certain set of inputs can be made to return any input, which can be dangerous depending on how applications use it. If an application treats arbitrary variants as trusted, this can lead to a variety of potential vulnerabilities like SQL injection or cross-site scripting (XSS).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2019-13146 concerns the Ruby field_test gem 0.3.0. The reported issue lets a value expected to come from a fixed set instead become arbitrary input. Business risk depends entirely on how an application uses that value, especially if it is trusted in database queries, rendered content, or security decisions. Exposure is most likely in Ruby applications using field_test 0.3.0 where variant values influence sensitive logic without independent validation. Applications not using this gem, not on 0.3.0, or validating returned values before use have less likely exposure. Treat this as a targeted dependency validation task, not an emergency by current evidence. Prioritize applications that use Ruby field_test 0.3.0 in user-facing decision, rendering, or data-access paths. Absence of CVSS and exploitation evidence lowers certainty, not the need to verify exposure. Mitigation focus: Inventory Ruby dependency manifests for field_test 0.3.0.; Check the gem page and GitHub issue for maintainer guidance.; Validate variant values against an application-owned allowlist before use..

Prepared

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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration 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-2019-13146 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.