CVE-2015-5636
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 · uneditedThe Newphoria Reversi application before 1.0.3 for Android and before 1.2 for iOS allows attackers to bypass a URL whitelist protection mechanism and obtain API access via unspecified vectors.
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 · moderate confidenceThe Newphoria Reversi mobile application for Android and iOS contained a flawed URL whitelist protection mechanism that could be bypassed by attackers, allowing unauthorized access to backend API endpoints. The vulnerability resided in the application's client-side validation of allowed URLs, which failed to properly restrict API access as intended.
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<= 1.0.2<= 1.1CVSS 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
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Check installed app version on AndroidOpen device Settings > Apps > Reversi and view the Version information, or use adb shell dumpsys package com.newphoria.reversi to retrieve versionName and versionCodeAffected if The version is 1.0.2 or earlier (versionCode lower than the build corresponding to 1.0.3)
-
Check installed app version on iOSOpen Settings > General > About > Reversi to view the Version number, or use idevicediagnostics -u or iTunes to inspect the app's Info.plist for CFBundleShortVersionStringAffected if The version is 1.1 or earlier (version number lower than 1.2)
-
Verify client-side URL whitelist validation existsFor Android, decompile the APK (using apktool) and search for URL whitelist logic in the source code (look for whitelist, allowedURL, validateUrl, or similar patterns). For iOS, analyze the binary or extracted code for similar validation functions.Affected if The application contains code that performs client-side validation of URLs against a whitelist array or list
-
Test whitelist bypass vulnerabilityIf client-side URL whitelist validation is present, intercept app traffic using a proxy (Burp Suite, mitmproxy) and attempt to modify request URLs to access API endpoints outside the declared whitelist by using URL manipulation techniques such as path traversal, parameter injection, or subdomain switchingAffected if API requests to non-whitelisted URLs succeed when they should be blocked, indicating the whitelist can be bypassed
A user is affected if they are running Reversi version 1.0.2 or earlier on Android or version 1.1 or earlier on iOS and the app contains exploitable client-side URL whitelist validation.
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 dataDevelopers should update to version 1.0.3+ (Android) or 1.2+ (iOS) which contain the fix. The fix requires implementing proper server-side validation of API requests and ensuring the whitelist cannot be bypassed through manipulation of request parameters or URLs.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5636 — 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-2015-5636 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