Outdated Minimum Platform Version Supported
The application can be installed on operating system versions that no longer receive security updates and lack protections it may rely on.
| Severity | Low |
| CVSS 3.1 | 3.6 CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 2 CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1104: Use of Unmaintained Third Party Components |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| Category | Outdated Components |
Description
The application declares a minimum platform version, the minSdk value on Android or the deployment target on iOS, old enough to allow installation on operating system releases that no longer receive security updates. Users on those releases remain exposed to publicly known vulnerabilities in the operating system and its components, so their devices, and with them the application's data, can be compromised, for example by a malicious application that gains elevated privileges or through flaws in outdated system components. The application also runs there without platform protections introduced in later versions, so its own protections, such as certificate validation that relies on platform defaults, may be weaker.
On Android, for example, devices before Android 7.0 trust user-installed certificate authorities by default and do not support network security configuration, devices before Android 5.0 cannot receive WebView updates separately from the operating system, and TLS 1.2 is not enabled by default before Android 5.0. Google's monthly Android Security Bulletins cover only recent Android releases, and Apple issues security fixes mainly for the current iOS release, back-porting some fixes to older ones. The risk depends on how many users run old versions and on whether an attacker can reach them, usually through a malicious application or a hostile network, so it is low for most applications and higher for those handling payments or sensitive personal data.
The weakness is identified from the package: the minimum SDK version in the decoded AndroidManifest.xml or in the output of aapt dump badging, and the MinimumOSVersion key in the iOS application's Info.plist. Static analysers such as MobSF report a low minimum SDK version. The finding concerns the oldest version permitted, not the target SDK version, which decides which newer platform behaviours the application opts in to.
Remediation
Align the minimum supported platform with versions that still receive security updates:
- Raise
minSdkin the application's Gradle configuration, and the minimum deployment target (IPHONEOS_DEPLOYMENT_TARGET) in Xcode, to versions that are still patched, weighing this against the share of users on older versions shown by the application's analytics. - Adopt a documented policy for reviewing the minimum version, for example whenever a platform version stops receiving security updates, and tell users in advance when support for a version will end.
- Where older versions must remain supported for a period, do not rely on platform defaults that have since changed: enable TLS 1.2 or later explicitly, and restrict trust to the system certificate authorities, or pin certificates, in the application's own networking code, as network security configuration has no effect before Android 7.0. Consider warning users of unpatched devices, for example by reading
Build.VERSION.SECURITY_PATCHon Android, and restricting high-risk functions for them. - For high-risk applications, check device integrity on the server, for example with the Play Integrity API, before allowing sensitive operations.
Confirm the fix by checking the minimum version declared in the next release build's manifest or Info.plist, and that installation is refused on a device running an older version.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.