Apple swift-asn1 up to 1.3.0 BER DER Parser syntactically invalid structure

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Apple swift-asn1 up to 1.3.0. Affected by this vulnerability is an unknown functionality of the component BER DER Parser. Such manipulation leads to improper handling of syntactically invalid structure. This vulnerability is uniquely identified as CVE-2025-0343. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability was found in Apple swift-asn1 up to 1.3.0 and classified as problematic. Affected by this issue is an unknown code block of the component BER DER Parser. The manipulation with an unknown input leads to a improper handling of syntactically invalid structure vulnerability. Using CWE to declare the problem leads to CWE-228. The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification. Impacted is availability. CVE summarizes:
Swift ASN.1 can be caused to crash when parsing certain BER/DER constructions. This crash is caused by a confusion in the ASN.1 library itself which assumes that certain objects can only be provided in either constructed or primitive forms, and will trigger a preconditionFailure if that constraint isn't met. Importantly, these constraints are actually required to be true in DER, but that correctness wasn't enforced on the early node parser side so it was incorrect to rely on it later on in decoding, which is what the library did. These crashes can be triggered when parsing any DER/BER format object. There is no memory-safety issue here: the crash is a graceful one from the Swift runtime. The impact of this is that it can be used as a denial-of-service vector when parsing BER/DER data from unknown sources, e.g. when parsing TLS certificates.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-0343 since 01/08/2025. The exploitation is known to be easy. There are neither technical details nor an exploit publicly available.
Upgrading to version 1.3.1 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.apple.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Improper handling of syntactically invalid structureCWE: CWE-228 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: swift-asn1 1.3.1
Timeline
01/08/2025 🔍01/14/2025 🔍
01/14/2025 🔍
02/19/2025 🔍
Sources
Vendor: apple.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2025-0343 (🔍)
GCVE (CVE): GCVE-0-2025-0343
GCVE (VulDB): GCVE-100-291632
Entry
Created: 01/14/2025 18:33Updated: 02/19/2025 04:55
Changes: 01/14/2025 18:33 (53), 01/15/2025 12:10 (1), 02/19/2025 04:55 (1)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.