OpenshiftApplication · Redhat
CVE-2019-19345
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 · uneditedA vulnerability was found in all openshift/mediawiki-apb 4.x.x versions prior to 4.3.0, where an insecure modification vulnerability in the /etc/passwd file was found in the container openshift/mediawiki-apb. An attacker with access to the container could use this flaw to modify /etc/passwd and escalate their privileges.
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 · high confidenceA privilege escalation vulnerability exists in openshift/mediawiki-apb versions 4.x.x prior to 4.3.0 where an attacker with container access can modify /etc/passwd to gain root privileges. The container lacks proper read-only protection of the /etc/passwd file.
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
OpenshiftApplication
>= 4.0, < 4.3= 3.11CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify deployed mediawiki-apb resourcesRun 'oc get deploymentconfig -A | grep -i mediawiki' or 'oc get pods -A | grep -i mediawiki' to find mediawiki-apb related deployments in the clusterAffected if Any mediawiki-apb deployment is found in the namespace
-
Determine mediawiki-apb image versionFor each mediawiki-apb deployment, run 'oc get deploymentconfig <name> -o jsonpath={.spec.template.spec.containers[*].image}' and check the image tag version. Compare against the affected range: 4.x.x prior to 4.3.0Affected if The image version is 4.x.x and is lower than 4.3.0, or the exact version cannot be determined but appears to be a pre-4.3.0 release
-
Check if /etc/passwd is writable from within the containerDeploy a test pod using the mediawiki-apb image and run: 'kubectl exec <pod> -- touch /etc/passwd.test' to test write access, or inspect container security context for 'readOnlyRootFilesystem' settingAffected if The container allows writing to /etc/passwd (test file creation succeeds) or the security context does not enforce read-only filesystem protection
-
Verify OpenShift version in useRun 'oc get clusterversion' to determine the OpenShift cluster versionAffected if The cluster version is >= 4.0 and < 4.3, or equals 3.11
A user is affected if they have deployed mediawiki-apb version 4.x.x prior to 4.3.0 on OpenShift >= 4.0, < 4.3 or 3.11, and the container allows modification of /etc/passwd without read-only filesystem protection.
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 data4.3
Update the mediawiki-apb container image to version 4.3.0 or later, and ensure container runtimes enforce read-only filesystem mounts where possible to prevent modification of sensitive system files.
Fix this in Openshift
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19345 — 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-19345 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