# CVE-2020-1982: PAN-OS: TLS 1.0 usage for certain communications with Palo Alto Networks cloud delivered services


- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Jul 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hmg3-8432-r83c

## What is CVE-2020-1982?

CVE-2020-1982 is a medium-severity vulnerability in Paloaltonetworks Pan-Os, published on 8 Jul 2020. 

### Official description

Certain communication between PAN-OS and cloud-delivered services inadvertently use TLS 1.0, which is known to be a cryptographically weak protocol. These cloud services include Cortex Data Lake, the Customer Support Portal, and the Prisma Access infrastructure. Conditions required for exploitation of known TLS 1.0 weaknesses do not exist for the communication between PAN-OS and cloud-delivered services. We do not believe that any communication is impacted as a result of known attacks against TLS 1.0. This issue impacts: All versions of PAN-OS 8.0; PAN-OS 8.1 versions earlier than PAN-OS 8.1.14; PAN-OS 9.0 versions earlier than PAN-OS 9.0.9; PAN-OS 9.1 versions earlier than PAN-OS 9.1.3. PAN-OS 7.1 is not impacted by this issue.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2020-1982?

It affects 1 product.


Products: Paloaltonetworks Pan-Os.

## How do I fix CVE-2020-1982?

No fix has been published for CVE-2020-1982 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-1982 being exploited?

There is no known exploitation of CVE-2020-1982 in the wild and no public exploit code.

## Other vulnerabilities in Paloaltonetworks Pan-Os

- [CVE-2024-3400](https://insights.sbomify.com/CVE-2024-3400/): Palo Alto Networks PAN-OS Command Injection (critical 10.0, exploited in the wild)
- [CVE-2020-2021](https://insights.sbomify.com/CVE-2020-2021/): Palo Alto Networks PAN-OS Authentication Bypass (critical 10.0, exploited in the wild)
- [CVE-2017-15944](https://insights.sbomify.com/CVE-2017-15944/): Palo Alto Networks PAN-OS Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2026-0300](https://insights.sbomify.com/CVE-2026-0300/): Palo Alto Networks PAN-OS Out-of-bounds Write (critical 9.3, exploited in the wild)
- [CVE-2024-0012](https://insights.sbomify.com/CVE-2024-0012/): Palo Alto Networks PAN-OS Management Interface Authentication Bypass (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1982 and fix it if it is affected.

What it is: CVE-2020-1982 is a medium-severity vulnerability in Paloaltonetworks Pan-Os, published on 8 Jul 2020. 
Exploitation: There is no known exploitation of CVE-2020-1982 in the wild and no public exploit code.

Affected product: Paloaltonetworks Pan-Os. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-1982/ (Markdown: https://insights.sbomify.com/CVE-2020-1982/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-1982
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-1982
- OSV: https://osv.dev/vulnerability/CVE-2020-1982

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-1982/
Summaries are generated and may contain mistakes; the official description above is the record.
