CVE-2019-16874
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPortainer before 1.22.1 has Incorrect Access Control (issue 2 of 4).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencePortainer before version 1.22.1 contains an Incorrect Access Control vulnerability (issue 2 of 4). This allows authenticated users to potentially access resources or perform actions they should not be authorized for, likely due to missing or improper authorization checks on certain API endpoints or functions within the container management interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.22.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Portainer is runningRun 'docker ps' and look for a container named 'portainer' or 'portainer-ce'Affected if A Portainer container is present in the output
-
Retrieve the Portainer versionRun 'docker inspect <portainer_container_id> --format={{.Config.Image}}' to get the image tag, or access the Portainer API at /api/system/status to retrieve the Version field from the JSON responseAffected if The version returned is below 1.22.1
-
Confirm API access to PortainerAttempt to reach the Portainer web interface or API endpoint over the configured port (typically 9000 or 9443)Affected if Portainer is accessible and you can authenticate to the interface
-
Check if authenticated users have elevated accessLog in as a standard authenticated user and attempt to access API endpoints outside your apparent authorization scope, such as /api/endpoints or /api/users, to observe if unauthorized resources are returnedAffected if A lower-privileged authenticated user can access resources or actions they should not be authorized for, indicating the access control flaw is present
You are affected if your Portainer version is below 1.22.1 and the application is accessible to authenticated users who may exploit the missing authorization checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.22.1
Upgrade Portainer to version 1.22.1 or later to obtain the corrected access control implementation. If immediate upgrade is not possible, restrict network access to the Portainer interface to trusted users only.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16874 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-16874 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data