VirtualSquare picoTCP/picoTCP-NG up to 2.1 Header Size unusual condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in VirtualSquare picoTCP and picoTCP-NG up to 2.1. Affected by this issue is some unknown functionality of the component Header Size Handler. Executing a manipulation can lead to an unknown weakness. This vulnerability is handled as CVE-2023-35849. There is not any exploit available. A patch should be applied to remediate this issue.
Details
A vulnerability has been found in VirtualSquare picoTCP and picoTCP-NG up to 2.1 and classified as problematic. This vulnerability affects an unknown function of the component Header Size Handler. The CWE definition for the vulnerability is CWE-754. The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. The impact remains unknown. CVE summarizes:
VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 does not properly check whether header sizes would result in accessing data outside of a packet.
The weakness was released 06/19/2023 as 4b9a16764f2b12b611de9c34a50b4713d10ca401. The advisory is available at github.com. This vulnerability was named CVE-2023-35849 since 06/19/2023. The technical details are unknown and an exploit is not available.
Applying the patch 4b9a16764f2b12b611de9c34a50b4713d10ca401 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-39842). If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
License
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: Unusual conditionCWE: CWE-754
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: 4b9a16764f2b12b611de9c34a50b4713d10ca401
Timeline
06/19/2023 🔍06/19/2023 🔍
06/19/2023 🔍
01/11/2026 🔍
Sources
Product: github.comAdvisory: 4b9a16764f2b12b611de9c34a50b4713d10ca401
Status: Confirmed
CVE: CVE-2023-35849 (🔍)
GCVE (CVE): GCVE-0-2023-35849
GCVE (VulDB): GCVE-100-231826
EUVD: 🔍
Entry
Created: 06/19/2023 06:59Updated: 01/11/2026 14:09
Changes: 06/19/2023 06:59 (40), 07/15/2023 08:12 (12), 01/11/2026 14:09 (16)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.