LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19334: Google Monorail before 2018-05-04 has a Cross-Site Search (XS-Search) vulnerability because CSV downloads a...

Google Monorail before 2018-05-04 has a Cross-Site Search (XS-Search) vulnerability because CSV downloads are affected by CSRF, and calculations of download times (for requests with an unsupported axis) can be used to obtain sensitive information about the content of bug reports.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-19334 is an information-disclosure issue in Google Monorail before 2018-05-04. A malicious site could potentially use a logged-in user's browser behavior and timing differences to infer sensitive details from bug reports. The sources do not provide a CVSS score or evidence of current exploitation.

Executive priority

Treat as a targeted confidentiality risk, especially where private bug reports contain vulnerability details or source-code references. Prioritize confirmation of patch status over emergency response unless an exposed legacy Monorail deployment is found.

Technical view

The vulnerability is described as XS-Search caused by CSRF exposure in CSV downloads. Timing calculations for requests with an unsupported axis could reveal information about bug report contents. The public record points to a Chromium infra commit dated 2018-05-04 as the relevant fix boundary.

Likely exposure

Exposure appears limited to Google Monorail deployments, forks, or hosted instances running code before 2018-05-04. Organizations only consuming modern maintained Monorail code are less likely to be exposed, but the source bundle does not confirm downstream patch status.

Exploitation context

The sources describe a browser-based side-channel against authenticated bug-tracker access, not public unauthenticated compromise. KEV is false, and the provided sources do not establish active exploitation in the wild.

Researcher notes

The record lacks CVSS, CWE classification, and detailed affected version metadata. Analysis should stay tied to the Monorail pre-2018-05-04 boundary and avoid assuming impact beyond sensitive bug-report inference through XS-Search timing behavior.

Mitigation direction

  • Confirm Monorail code includes the 2018-05-04 Chromium infra fix boundary.
  • Check current vendor or project guidance for any additional remediation.
  • Restrict access to private bug reports to users with clear business need.
  • Review CSV download endpoints for CSRF protections and safe error handling.

Validation and detection

  • Inventory Monorail instances, forks, and deployment versions.
  • Verify the referenced Chromium infra commit or later equivalent is present.
  • Review application tests covering CSV downloads and unsupported-axis requests.
  • Assess private bug-report exposure using authorized, non-destructive testing only.
Prepared
Confidence
medium
Sources
5

Public sources used

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-2018-19334 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
4Source 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.