Skip to content

fix(security): SEC-619 raise minimum deployment target to iOS 17#80

Open
juwoncube wants to merge 1 commit into
release/v2.3.0from
release/v2.3.1
Open

fix(security): SEC-619 raise minimum deployment target to iOS 17#80
juwoncube wants to merge 1 commit into
release/v2.3.0from
release/v2.3.1

Conversation

@juwoncube

Copy link
Copy Markdown

Why

Pen test (SEC-619) flags EOL minimum OS versions in embedded frameworks of the Blood iOS app. ThunderTable declared iOS 15.0/16.0 deployment targets, which are end-of-life.

What changed

  • Raised IPHONEOS_DEPLOYMENT_TARGET to 17.0 on all build configurations (framework, tests, demo app) in project.pbxproj
  • Bumped MARKETING_VERSION to 2.3.1
  • No Package.swift, podspec, xcconfig, or Cartfile present — no other deployment-target declarations to update

Build / test results

  • xcodebuild build (ThunderTable scheme, generic/platform=iOS): BUILD SUCCEEDED
  • xcodebuild test (ThunderTableTests scheme, iPhone 16 Pro simulator): TEST SUCCEEDED — 3 tests, 0 failures

New warnings

No new deprecation warnings introduced by the bump (only pre-existing, unrelated appintentsmetadataprocessor metadata notice).

Note for consumers

Consumer apps must target iOS >= 17 to adopt this version.

Raise IPHONEOS_DEPLOYMENT_TARGET to 17.0 across all targets and bump
MARKETING_VERSION to 2.3.1.
@semgrep-code-3sidedcube

Copy link
Copy Markdown

Semgrep found 1 ATS-consider-pinning finding:

The application's App Transport Security (ATS) configuration does not leverage the in-built public key pinning mechanisms. The application should consider leverage ATS public key pinning to ensure that the application only communicates to serves with an allow-listed certificate (and public key). By default the device will allow connections if the default trust store (CA store) posesses the right certificates. The number of accepted Certificate Authorities by default is hundreds. Using public key pinning vastly reduces the attack surface.

@juwoncube juwoncube changed the base branch from master to release/v2.3.0 June 3, 2026 17:22
@juwoncube juwoncube requested a review from a team as a code owner June 3, 2026 17:22
@juwoncube juwoncube requested review from 3scsamdavis, JonValijonov, Szuyun-3SC and neil3sidedcube and removed request for a team June 3, 2026 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants