# CVE-2017-9045: Information disclosure in n/a

> Man-in-the-middle attackers can spoof feed and schedule data by intercepting unencrypted JSON downloads in the Google I/O Android app.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-97hx-9873-chw2

## What is CVE-2017-9045?

CVE-2017-9045 is a medium-severity vulnerability in n/a, published on 18 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Google I/O 2017 application before 5.1.4 for Android downloads multiple .json files from http://storage.googleapis.com without SSL, which makes it easier for man-in-the-middle attackers to spoof Feed and Schedule data by creating a modified blocks_v4.json file.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2017-9045?

It affects 1 product.


Products: Google Google I\/O 2017.

## How do I fix CVE-2017-9045?

No fix has been published for CVE-2017-9045 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-9045 being exploited?

There is no known exploitation of CVE-2017-9045 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-9045 and fix it if it is affected.

What it is: CVE-2017-9045 is a medium-severity vulnerability in n/a, published on 18 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-9045 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-9045/ (Markdown: https://insights.sbomify.com/CVE-2017-9045/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-9045
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-9045
- OSV: https://osv.dev/vulnerability/CVE-2017-9045

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-9045/
Summaries are generated and may contain mistakes; the official description above is the record.