VirtualSquare picoTCP/picoTCP-NG up to 2.1 MSS Structure Member calculation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in VirtualSquare picoTCP and picoTCP-NG up to 2.1. Affected by this vulnerability is an unknown functionality of the component MSS Structure Member Handler. Performing a manipulation results in an unknown weakness. This vulnerability is known as CVE-2023-35848. No exploit is available. It is suggested to install a patch to address this issue.
Details
A vulnerability, which was classified as problematic, was found in VirtualSquare picoTCP and picoTCP-NG up to 2.1. This affects some unknown processing of the component MSS Structure Member Handler. CWE is classifying the issue as CWE-682. The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management. The impact remains unknown. The summary by CVE is:
VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 lacks certain size calculations before attempting to set a value of an mss structure member.
The weakness was published 06/19/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-35848 since 06/19/2023. Neither technical details nor an exploit are publicly available.
Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-39841). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
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: CalculationCWE: CWE-682
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
06/19/2023 🔍06/19/2023 🔍
06/19/2023 🔍
01/11/2026 🔍
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CVE: CVE-2023-35848 (🔍)
GCVE (CVE): GCVE-0-2023-35848
GCVE (VulDB): GCVE-100-231825
EUVD: 🔍
Entry
Created: 06/19/2023 06:59Updated: 01/11/2026 14:09
Changes: 06/19/2023 06:59 (38), 07/15/2023 08:08 (12), 01/11/2026 14:09 (15)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.