[Bug] Security scanner flags vulnerable Guava 31.1-android in firebase-analytics (even in v24.0.0)

Open
#8,770 1 comment 2 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
android, java
Domain
backend, security

Research direction

Start by tracing the dependency declarations for firebase-analytics and play-services-measurement-impl in the repository, then check how their published dependency versions are managed. Confirm whether the Guava version can be updated safely across the affected artifacts; done means the dependency tree resolves to a patched Guava version and the affected SDK builds and tests pass.

Written by the indexing model from the issue text.

Description

api: analytics
Description:

When generating an SBOM and running a security scan using Grype, the build fails due to a vulnerable version of Guava (31.1-android) being pulled in transitively by firebase-analytics.

I am currently using firebase-bom: 33.9.0, which resolves firebase-analytics to 22.2.0. I noticed a similar report in #7583, but I want to highlight that simply updating to the latest firebase-analytics: 24.0.0 does not resolve this issue, as its underlying play-services-measurement-impl dependency still relies on the same vulnerable Guava version.

Vulnerabilities Flagged (Grype):

GHSA-xxph-c9ww-hj94 (High) - CompactHashMap/CompactHashSet/MapMakerInternalMap deserialization triggers uncontrolled memory allocation

GHSA-7g45-4rm6-3mm3 (Medium) - Insecure use of temporary directory

GHSA-5mg8-w23w-74h3 (Low) - Information Disclosure in Guava

Dependency Tree Context:
+--- com.google.firebase:firebase-analytics:22.2.0 (and 24.0.0)
|    +--- com.google.android.gms:play-services-measurement:22.2.0 (and 24.0.0)
|    |    +--- com.google.android.gms:play-services-measurement-impl:22.2.0 (and 24.0.0)
|    |    |    \--- com.google.guava:guava:31.1-android
Expected Behavior:

The Firebase Android SDK and its underlying Google Play Services dependencies should use a patched version of Guava (such as 33.7.2-android) to prevent CI/CD security scanners from blocking app releases.

Actual Behavior:

The SDK pulls in Guava 31.1-android, forcing developers to manually implement project-wide dependency constraints to override the version and clear security warnings.

Environment:

Firebase BOM: 33.9.0

Firebase Analytics: 22.2.0 (also verified issue exists in 24.0.0)

Scanner: Grype 0.121.0

Dominant language
Java
Stars
2.6k
Forks
733
Avg merge
2d 15h
Merged PRs (30d)
72

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/firebase-android-sdk

All issues in firebase/firebase-android-sdk

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.