{"answers":{"affected":"2 open source packages ship an affected version, including org.openrefine:openrefine.","exploited":"There is no known exploitation of GHSA-3pg4-qwc8-426r in the wild and no public exploit code.","fix":"Upgrade org.openrefine:openrefine to 3.8.3 or later.","what":"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."},"fix_prompt":"Check this codebase for GHSA-3pg4-qwc8-426r and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of GHSA-3pg4-qwc8-426r in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.openrefine:openrefine (Maven): affected all versions; fixed in 3.8.3\n- org.openrefine:openrefine (Maven): affected all versions; fixed in 3.8.3\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-3pg4-qwc8-426r/ (Markdown: https://insights.sbomify.com/GHSA-3pg4-qwc8-426r/index.md)","id":"GHSA-3pg4-qwc8-426r","markdown":"https://insights.sbomify.com/GHSA-3pg4-qwc8-426r/index.md","name":"GHSA-3pg4-qwc8-426r","record":{"aliases":[],"analysis":{"component_type":"desktop_application","fix_type":"configuration_change","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenRefine data tool","requires_auth":"none","summary":"Hardcoded Google API credentials in OpenRefine allow attackers to impersonate the application and request access to user accounts.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nOpenRefine 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.\nThis archive then contains the file `com/google/refine/extension/gdata/GoogleAPIExtension.java`, which contains the following lines:\n\n```java\n    // For a production release, the second parameter (default value) can be set\n    // for the following three properties (client_id, client_secret, and API key) to\n    // the production values from the Google API console\n    private static final String CLIENT_ID = System.getProperty(\"ext.gdata.clientid\", new String(Base64.getDecoder().decode(\"ODk1NTU1ODQzNjMwLWhkZWwyN3NxMDM5ZjFwMmZ0aGE2M2VvcWFpY2JwamZoLmFwcHMuZ29vZ2xldXNlcmNvbnRlbnQuY29t\")));\n    private static final String CLIENT_SECRET = System.getProperty(\"ext.gdata.clientsecret\", new String(Base64.getDecoder().decode(\"R2V2TnZiTnA2a3IxeDd5c3VZNENmYlNo\")));\n```\n\nThe Base64 encoding can then be decoded to obtain the client id and client secret.\nThose 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.\n\n### Patches\n\nThe bundled credentials should be revoked.\n\n### Workarounds\n\nUsers should revoke access to their Google account if they have connected it to OpenRefine.","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"OpenRefine leaks Google API credentials in releases","id":"GHSA-3pg4-qwc8-426r","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"hardcoded_credentials","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["3.8.3"],"introduced":["0"],"last_affected":[],"package":"org.openrefine:openrefine","purl":null,"source":"GHSA-3pg4-qwc8-426r"},{"ecosystem":"Maven","fixed":["3.8.3"],"introduced":["0"],"last_affected":[],"package":"org.openrefine:openrefine","purl":"pkg:maven/org.openrefine/openrefine","source":"GHSA-3pg4-qwc8-426r"}],"products":null,"published":"2024-10-24","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Hardcoded Google API credentials in OpenRefine allow attackers to impersonate the application and request access to user accounts.","url":"https://insights.sbomify.com/GHSA-3pg4-qwc8-426r/"}