What is GHSA-3HPF-FF72-J67P?

GHSA-3HPF-FF72-J67P is a low-severity insecure deserialization vulnerability in shared_preferences_android (pub), affecting versions = 2.3.3. It is fixed in 2.3.4. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.

How severe is GHSA-3HPF-FF72-J67P?

GHSA-3HPF-FF72-J67P has a CVSS score of 3.0 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of shared_preferences_android are affected by GHSA-3HPF-FF72-J67P?

shared_preferences_android (pub) versions = 2.3.3 is affected.

Is there a fix for GHSA-3HPF-FF72-J67P?

Yes. GHSA-3HPF-FF72-J67P is fixed in 2.3.4. Upgrade to this version or later.

Is GHSA-3HPF-FF72-J67P exploitable, and should I be worried?

Whether GHSA-3HPF-FF72-J67P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-3HPF-FF72-J67P is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-3HPF-FF72-J67P?

Upgrade shared_preferences_android to 2.3.4 or later.

GHSA-3HPF-FF72-J67P in shared_preferences_android

Summary

sharedpreferencesandroid vulnerability

Workarounds

Update to the latest version of shared_preferences_android that contains the changes to address this vulnerability.

References

TBD

For more information

See our community page to find ways to contact the team.

Thanks

Thank you so much to Oskar Zeino-Mahmalat from sonarsource for finding and reporting this issue!

Impact

Due to some data types not being natively representable for the available storage options, shared_preferences_android serializes and deserializes special string prefixes to store these unrepresentable data types. This allows arbitrary classes to be deserialized leading to arbitrary code execution.

As a result, Files containing the preferences can be overwritten with a malicious one with a deserialization payload that triggers as soon as the data is loaded from the disk.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

GHSA-3HPF-FF72-J67P has a CVSS score of 3.0 (Low). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.3.4); upgrading removes the vulnerable code path.

Affected versions

shared_preferences_android (= 2.3.3)

Security releases

shared_preferences_android → 2.3.4 (pub)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

2.3.4

Frequently Asked Questions

What is GHSA-3HPF-FF72-J67P? GHSA-3HPF-FF72-J67P is a low-severity insecure deserialization vulnerability in shared_preferences_android (pub), affecting versions = 2.3.3. It is fixed in 2.3.4. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
How severe is GHSA-3HPF-FF72-J67P? GHSA-3HPF-FF72-J67P has a CVSS score of 3.0 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of shared_preferences_android are affected by GHSA-3HPF-FF72-J67P? shared_preferences_android (pub) versions = 2.3.3 is affected.
Is there a fix for GHSA-3HPF-FF72-J67P? Yes. GHSA-3HPF-FF72-J67P is fixed in 2.3.4. Upgrade to this version or later.
Is GHSA-3HPF-FF72-J67P exploitable, and should I be worried? Whether GHSA-3HPF-FF72-J67P is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-3HPF-FF72-J67P is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-3HPF-FF72-J67P? Upgrade shared_preferences_android to 2.3.4 or later.