CVE-2024-33662: Portainer before 2.20.2 improperly uses an encryption algorithm in the AesEncrypt function.
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: github.com/portainer/portainer (Go) 2.20.2; govulncheck-vulndb (openSUSE:Leap 15.5) 0.0.20241030T212825-150000.1.9.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20241030T212825-1.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to github.com/portainer/portainer (Go) 2.20.2; govulncheck-vulndb (openSUSE:Leap 15.5) 0.0.20241030T212825-150000.1.9.1; govulncheck-vulndb (openSUSE:Tumbleweed) 0.0.20241030T212825-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- Oct 2, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 20th percentile
- CWE
- CWE-326
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Check your site's encryptionRun the SSL check
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| portainer | portainer | cpe:2.3:a:portainer:portainer |
Check your site's encryption
This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.
Run the SSL checkAffected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- portainer portainerbefore 2.20.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/portainer/portainer | from 0 | — |
| Go | github.com/portainer/portainer | before 2.20.2 | 2.20.2 |
| openSUSE:Leap 15.5 | govulncheck-vulndb | before 0.0.20241030T212825-150000.1.9.1 | 0.0.20241030T212825-150000.1.9.1 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20241030T212825-1.1 | 0.0.20241030T212825-1.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP5 | govulncheck-vulndb | before 0.0.20241030T212825-150000.1.9.1 | 0.0.20241030T212825-150000.1.9.1 |
| SUSE:Package Hub 12 | govulncheck-vulndb | before 0.0.20241104T154416-5.1 | 0.0.20241104T154416-5.1 |
Same product
portainer: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-24264Portainer 1.24.1 and earlier is affected by incorrect access control that may lead to remote arbitrary code execution.40Plan
- CVE-2018-19466A vulnerability was found in Portainer before 1.20.0.40Plan
- CVE-2018-12678Portainer before 1.18.0 supports unauthenticated requests to the websocket endpoint with an unvalidated id query parameter for the…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2024-29296Apr 10, 2024 · A user enumeration vulnerability was found in Portainer CE 2.19.4.21Monitor
- ← EarlierCVE-2024-33661Apr 25, 2024 · Portainer before 2.20.0 allows redirects when the target is not index.yaml.36Monitor
- Later →CVE-2025-49593Jun 17, 2025 · Portainer HTTP Headers May Leak to Malicious Container Registries27Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/portainer/portainer | 2.20.2 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20241030T212825-150000.1.9.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20241030T212825-150000.1.9.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1599 · Oct 3, 2024(Portrainer Güvenlik Zafiyeti)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-326 · Inadequate Encryption StrengthCVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.