| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in usrsctp. It has been rated as problematic. Impacted is the function sctp_load_addresses_from_init. Performing a manipulation results in out-of-bounds.
This vulnerability is cataloged as CVE-2019-20503. It is possible to initiate the attack remotely. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability, which was classified as problematic, was found in usrsctp (version unknown). This affects the function sctp_load_addresses_from_init. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality. The summary by CVE is:
usrsctp before 2019-12-20 has out-of-bounds reads in sctp_load_addresses_from_init.
The weakness was shared 03/06/2020. This vulnerability is uniquely identified as CVE-2019-20503 since 03/06/2020. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
Upgrading eliminates this vulnerability.
The entries VDB-155704 and VDB-155815 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Out-of-boundsCWE: CWE-125 / CWE-119
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Patch: github.com
Timeline
03/06/2020 🔍03/06/2020 🔍
03/07/2020 🔍
05/12/2025 🔍
Sources
Advisory: RHSA-2020:0815Status: Confirmed
CVE: CVE-2019-20503 (🔍)
GCVE (CVE): GCVE-0-2019-20503
GCVE (VulDB): GCVE-100-150969
See also: 🔍
Entry
Created: 03/07/2020 10:08Updated: 05/12/2025 12:16
Changes: 03/07/2020 10:08 (35), 03/07/2020 10:13 (17), 04/09/2024 19:10 (20), 04/09/2024 19:18 (1), 06/27/2024 18:50 (1), 05/12/2025 12:16 (5)
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.