PatchTheCVEvirtualsquare vulnerabilities
Recent CVEs affecting virtualsquare products. 4 tracked.
virtualsquare has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2023-06-19. Highest priority: CVE-2023-35848 (score 45/100).
- CVE-2023-35849 HIGH 7.5 UPGRADE VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 does not properly check whether header sizes would result i
- CVE-2023-35848 HIGH 7.5 UPGRADE VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 lacks certain size calculations before attempting to set a
- CVE-2023-35847 HIGH 7.5 UPGRADE VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 does not have an MSS lower bound (e.g., it could be zero).
- CVE-2023-35846 HIGH 7.5 UPGRADE VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 does not check the transport layer length in a frame before
FAQ
How do I fix virtualsquare vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is virtualsquare being exploited right now?
None of the tracked virtualsquare CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which virtualsquare CVE should I patch first?
CVE-2023-35848 currently ranks highest (45/100): VirtualSquare picoTCP (aka PicoTCP-NG) through 2.1 lacks certain size calculations before attempting to set a .