CVE-2023-28387
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited"NewsPicks" App for Android versions 10.4.5 and earlier and "NewsPicks" App for iOS versions 10.4.2 and earlier use hard-coded credentials, which may allow a local attacker to analyze data in the app and to obtain API key for an external service.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe NewsPicks Android (v10.4.5 and earlier) and iOS (v10.4.2 and earlier) applications contain hard-coded credentials embedded in the app binary. A local attacker with physical or filesystem access to the device or the app package can extract these credentials, which include API keys for external services, enabling unauthorized API access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.4.2<= 10.4.5CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if NewsPicks app is installedCheck device for Uzabase Newspicks application. On Android: Settings > Apps > NewsPicks. On iOS: Check home screen or Settings > General > iPhone Storage for the app.Affected if The NewsPicks app is present on the device.
-
Determine installed version on AndroidOpen Google Play Store app page for NewsPicks or go to Settings > Apps > NewsPicks > App info to view the version number.Affected if Version is 10.4.5 or earlier on Android.
-
Determine installed version on iOSOpen App Store app page for NewsPicks or go to Settings > General > iPhone Storage > NewsPicks to view the version.Affected if Version is 10.4.2 or earlier on iOS.
-
Inspect Android app binary for embedded credentialsExtract the APK file from the device or download it from a third-party APK site. Use unzip to extract contents, then run 'strings' command or search for patterns like 'api', 'key', 'secret', 'token' in the lib folder or assets. Look for AWS keys, Firebase tokens, or third-party service credentials in plaintext.Affected if Hardcoded API keys, secrets, tokens, or credentials are found in the app binary.
-
Inspect iOS app binary for embedded credentialsExtract the IPA file (rename to .zip and unzip). Search using 'strings' or grep for patterns like 'api_key', 'apikey', 'secret', 'token', 'password' within the Payload folder. Examine .plist files and binary executables for plaintext credentials.Affected if Hardcoded API keys, secrets, tokens, or credentials are found in the app binary.
A user is affected if they have NewsPicks installed with Android version 10.4.5 or earlier or iOS version 10.4.2 or earlier, and the app binary contains embedded credentials that can be extracted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRemove all hard-coded credentials from the application binaries and implement secure credential management (e.g., token-based authentication, keyvault services, or runtime secrets injection). Rotate any exposed API keys immediately and update both Android and iOS apps to versions that no longer contain embedded secrets.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-28387 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-28387 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data