LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19335: Google Monorail before 2018-06-07 has a Cross-Site Search (XS-Search) vulnerability because CSV downloads a...

Google Monorail before 2018-06-07 has a Cross-Site Search (XS-Search) vulnerability because CSV downloads are affected by CSRF, and calculations of download times (for requests with a crafted groupby value) 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-19335 is an information-leak issue in Google Monorail, Google’s issue tracker software, before 2018-06-07. A web attacker could abuse cross-site CSV downloads and response timing differences to infer sensitive information from bug reports. Evidence does not show active exploitation, and no CVSS score is provided.

Executive priority

Treat this as a targeted data-confidentiality risk for affected issue trackers, not a broad emergency. Prioritize remediation if Monorail stores vulnerability reports, source-code references, or unreleased product security details.

Technical view

The vulnerability is described as Cross-Site Search (XS-Search). CSV downloads were affected by CSRF, and crafted groupby values could change download timing in ways that exposed information about bug report contents. The public record identifies Google Monorail before 2018-06-07 and references a Chromium infra commit.

Likely exposure

Exposure is likely limited to organizations running Google Monorail or forks older than 2018-06-07. General users of unrelated Google services are not identified as affected in the provided sources.

Exploitation context

The provided sources describe a timing-based browser attack class, not a public weaponized exploit campaign. CISA KEV is false, so active exploitation should not be assumed from this bundle.

Researcher notes

The key uncertainty is missing severity scoring and limited affected-product metadata. Analysis should stay anchored to Monorail before 2018-06-07, CSRF on CSV downloads, crafted groupby timing behavior, and the referenced Chromium infra change.

Mitigation direction

  • Inventory Monorail deployments and forks for builds before 2018-06-07.
  • Check the referenced Chromium infra commit and Monorail guidance for the fixed behavior.
  • Upgrade affected Monorail deployments to a post-2018-06-07 revision.
  • Restrict access to sensitive bug reports using least privilege.
  • Review CSV download endpoints for CSRF protections and safe query handling.

Validation and detection

  • Confirm whether any Monorail instance or fork exists in production.
  • Verify deployed revision date is after 2018-06-07 or includes the referenced commit.
  • Check that CSV downloads require valid authorization and anti-CSRF controls.
  • Review logs for unusual CSV download activity against sensitive bug trackers.
  • Confirm private bug report data is not exposed through timing-observable endpoints.
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-19335 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.