# GHSA-3pg4-qwc8-426r: OpenRefine leaks Google API credentials in releases

> Hardcoded Google API credentials in OpenRefine allow attackers to impersonate the application and request access to user accounts.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Oct 2024

## What is GHSA-3pg4-qwc8-426r?

GHSA-3pg4-qwc8-426r is a vulnerability in org.openrefine:openrefine, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Impact

OpenRefine releases contain Google API authentication keys ("client id" and "client secret") which can be extracted from released artifacts. For instance, download the package for OpenRefine 3.8.2 on linux. It contains the file `openrefine-3.8.2/webapp/extensions/gdata/module/MOD-INF/lib/openrefine-gdata.jar`, which can be extracted.
This archive then contains the file `com/google/refine/extension/gdata/GoogleAPIExtension.java`, which contains the following lines:

```java
    // For a production release, the second parameter (default value) can be set
    // for the following three properties (client_id, client_secret, and API key) to
    // the production values from the Google API console
    private static final String CLIENT_ID = System.getProperty("ext.gdata.clientid", new String(Base64.getDecoder().decode("ODk1NTU1ODQzNjMwLWhkZWwyN3NxMDM5ZjFwMmZ0aGE2M2VvcWFpY2JwamZoLmFwcHMuZ29vZ2xldXNlcmNvbnRlbnQuY29t")));
    private static final String CLIENT_SECRET = System.getProperty("ext.gdata.clientsecret", new String(Base64.getDecoder().decode("R2V2TnZiTnA2a3IxeDd5c3VZNENmYlNo")));
```

The Base64 encoding can then be decoded to obtain the client id and client secret.
Those credentials can then be used by other applications to request access to Google accounts, pretending they are OpenRefine. This assumes that they also get access to the user access tokens, which this vulnerability doesn't expose by itself.

### Patches

The bundled credentials should be revoked.

### Workarounds

Users should revoke access to their Google account if they have connected it to OpenRefine.

## Which versions are affected by GHSA-3pg4-qwc8-426r?

2 open source packages ship an affected version, including org.openrefine:openrefine.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.openrefine:openrefine` | Maven | All versions | 3.8.3 |
| `org.openrefine:openrefine` | Maven | All versions | 3.8.3 |

## How do I fix GHSA-3pg4-qwc8-426r?

Upgrade org.openrefine:openrefine to 3.8.3 or later.

## Is GHSA-3pg4-qwc8-426r being exploited?

There is no known exploitation of GHSA-3pg4-qwc8-426r in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3pg4-qwc8-426r and fix it if it is affected.

What it is: GHSA-3pg4-qwc8-426r is a vulnerability in org.openrefine:openrefine, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-3pg4-qwc8-426r in the wild and no public exploit code.

Affected packages and fixed versions:
- org.openrefine:openrefine (Maven): affected all versions; fixed in 3.8.3
- org.openrefine:openrefine (Maven): affected all versions; fixed in 3.8.3

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/GHSA-3pg4-qwc8-426r/ (Markdown: https://insights.sbomify.com/GHSA-3pg4-qwc8-426r/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3pg4-qwc8-426r

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3pg4-qwc8-426r/
Summaries are generated and may contain mistakes; the official description above is the record.