libpano13 up to 2.9.20~rc2+dfsg-3 panoFileOutputNamesCreate format string
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in libpano13 up to 2.9.20~rc2+dfsg-3. The affected element is the function panoFileOutputNamesCreate. The manipulation leads to format string.
This vulnerability is traded as CVE-2021-20307. There is no exploit available.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in libpano13 up to 2.9.20~rc2+dfsg-3 and classified as critical. This issue affects the function panoFileOutputNamesCreate. The manipulation with an unknown input leads to a format string vulnerability. Using CWE to declare the problem leads to CWE-134. The product uses a function that accepts a format string as an argument, but the format string originates from an external source. Impacted is confidentiality, integrity, and availability.
The weakness was shared 04/06/2021. The advisory is shared at bugzilla.redhat.com. The identification of this vulnerability is CVE-2021-20307. Technical details are known, but no exploit is available.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at sourceforge.net.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.5
VulDB Temp Score: 5.5
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: Format stringCWE: CWE-134 / CWE-119
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: sourceforge.net
Timeline
12/17/2020 🔍04/06/2021 🔍
04/06/2021 🔍
04/10/2021 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2021-20307 (🔍)
GCVE (CVE): GCVE-0-2021-20307
GCVE (VulDB): GCVE-100-172409
Entry
Created: 04/06/2021 08:03Updated: 04/10/2021 09:37
Changes: 04/06/2021 08:03 (37), 04/10/2021 09:37 (2)
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.