CVE-2023-23131
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 · uneditedSelfwealth iOS mobile App 3.3.1 is vulnerable to Insecure App Transport Security (ATS) Settings.
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 confidenceSelfwealth iOS mobile App version 3.3.1 has insecure App Transport Security (ATS) settings configured, which weakens or disables the security protections that require encrypted HTTPS connections. This misconfiguration could allow sensitive data to be transmitted over unencrypted or improperly validated connections, potentially enabling man-in-the-middle attacks.
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= 3.3.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 installed Selfwealth app versionOpen the App Store, search for Selfwealth, and check the current version; or open the app and navigate to Settings > About to view the version numberAffected if The installed version is exactly 3.3.1
-
Locate the app's Info.plist fileObtain the Selfwealth app binary (.ipa file), extract it, and navigate to the Payload folder to find Info.plist inside the app bundleAffected if The Info.plist file exists in the app bundle
-
Check for NSAllowsArbitraryLoads settingOpen Info.plist in a text editor or plist viewer and search for the key 'NSAllowsArbitraryLoals' (or NSAllowsArbitraryLoadsForMedia, NSAllowsArbitraryLoadsInWebContent)Affected if Any of these keys are set to true or YES, indicating ATS is disabled for web content or all loads
-
Verify other ATS-weakening configurationsExamine Info.plist for keys like NSAllowsInvalidCertificates, NSExceptionMinimumTLSVersion set to lower values like TLSv1.0, or NSExceptionRequiresForwardSecrecy set to NOAffected if Any of these security-weakening ATS exceptions are present in the configuration
-
Confirm HTTPS enforcement is missingVerify that there are no NSExceptionDomains entries with proper minimum TLS requirements or that the app lacks strict NSAllowsArbitraryLoads = NO defaultsAffected if The app does not enforce validated HTTPS for all connections and permits unencrypted or improperly validated network traffic
A user is affected if the Selfwealth iOS app version is 3.3.1 AND the Info.plist contains any NSAllowsArbitraryLoads or similar ATS-weakening keys set to true/YES, allowing unencrypted or insecure connections.
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 dataReview and correct the ATS configuration in the application's Info.plist file to enforce proper security settings, including disabling arbitrary loads and ensuring all network connections use validated HTTPS.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23131 — 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-23131 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