LiveActive security incident?Get immediate response
CVE Record

CVE-2018-19367: Portainer through 1.19.2 provides an API endpoint (/api/users/admin/check) to verify that the admin user is...

Portainer through 1.19.2 provides an API endpoint (/api/users/admin/check) to verify that the admin user is already created. This API endpoint will return 404 if admin was not created and 204 if it was already created. Attackers can set an admin password in the 404 case.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Portainer versions through 1.19.2 exposed a setup-state check that could tell whether the admin account existed. If it did not, an attacker could set the admin password. The business risk is unauthorized control of a container management interface, especially where Portainer is internet reachable or left uninitialized.

Executive priority

Prioritize exposed or uninitialized Portainer systems because compromise could give an attacker administrative control over container infrastructure. Treat as urgent where Portainer is internet-facing, but note that the provided sources do not confirm active exploitation or a CVSS score.

Technical view

The reported issue is in Portainer through 1.19.2 at /api/users/admin/check. The endpoint returns 404 when admin is not created and 204 when it exists. In the 404 state, attackers can set an admin password. The sources do not provide CVSS, CWE, confirmed fixed version, or exploit telemetry.

Likely exposure

Exposure is most likely on Portainer deployments through 1.19.2 that are reachable by untrusted networks and have not completed admin initialization. Internet-facing management consoles are the highest concern. The supplied affected metadata is incomplete, but the CVE description names Portainer through 1.19.2.

Exploitation context

CISA KEV status is false in the provided bundle, and no supplied source confirms active exploitation. The referenced Shodan-related repository suggests public interest in finding exposed Portainer instances, but that is not proof of exploitation.

Researcher notes

Evidence is limited to the CVE description and linked public references. The key condition is the 404 state on the admin-check endpoint before admin creation. Avoid assuming all Portainer deployments are vulnerable; validate version, network exposure, and initialization state.

Mitigation direction

  • Identify all Portainer deployments and their versions.
  • Check Portainer vendor guidance for the fixed or supported upgrade path.
  • Restrict Portainer UI and API access to trusted administrative networks.
  • Ensure every deployment has completed secure admin initialization.
  • Review access controls and credentials for exposed or legacy instances.

Validation and detection

  • Inventory Portainer instances and confirm whether any are version 1.19.2 or older.
  • Verify Portainer is not reachable from the public internet unless explicitly required.
  • Confirm the admin account is already initialized on each deployment.
  • Review logs for unexpected admin setup or authentication activity.
  • Document any exposed legacy instance for urgent remediation tracking.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-19367 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.