CVE-2019-3899
published 2019-04-22CVE-2019-3899: It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only…
PriorityP351critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
1.41%
69.9th percentile
It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only affects heketi as shipped with Openshift Container Platform 3.11.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| redhat | openshift_container_platform | — | — |
| the_heketi_project | heketi | — | — |
CVSS provenance
nvdv3.19.8CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvdv3.07.3HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
nvdv2.07.5HIGHAV:N/AC:L/Au:N/C:P/I:P/A:P
vendor_redhat9.8CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
heketi: heketi can be installed using insecure defaults
vendor_redhat·2019-04-18·CVSS 9.8
CVE-2019-3899 [CRITICAL] CWE-287 heketi: heketi can be installed using insecure defaults
heketi: heketi can be installed using insecure defaults
It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only affects heketi as shipped with Openshift Container Platform 3.11.
It was found that the default configuration of Heketi does not require any authentication, potentially exposing the Heketi server API to be misused. An unauthenticated attacker could connect remotely to Heketi Server and run arbitrary commands supported by Heketi Server API via Heketi CLI.
Mitigation: After installation of Heketi
1. configure user and admin key in /etc/heketi/heketi.json file
...
{
"_port_comment": "Heketi Server Port Number",
"port": "8080",
"_use_auth": "Enable JWT authorization. Please enable
GHSA
GHSA-g8m6-5j3r-8xg4: It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse
ghsa_unreviewed·2022-05-24
CVE-2019-3899 [CRITICAL] CWE-306 GHSA-g8m6-5j3r-8xg4: It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse
It was found that default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse. This isue only affects heketi as shipped with Openshift Container Platform 3.11.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-3899 heketi: heketi can be installed using insecure defaults [fedora-all]
bugzilla·2019-05-03·CVSS 9.8
CVE-2019-3899 [CRITICAL] CVE-2019-3899 heketi: heketi can be installed using insecure defaults [fedora-all]
CVE-2019-3899 heketi: heketi can be installed using insecure defaults [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported ver
Bugzilla
CVE-2019-3899 heketi: heketi can be installed using insecure defaults [fedora-all]
bugzilla·2019-05-03·CVSS 9.8
CVE-2019-3899 [CRITICAL] CVE-2019-3899 heketi: heketi can be installed using insecure defaults [fedora-all]
CVE-2019-3899 heketi: heketi can be installed using insecure defaults [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported ver
Bugzilla
CVE-2019-3899 heketi: heketi can be installed using insecure defaults
bugzilla·2019-04-18·CVSS 9.8
CVE-2019-3899 [CRITICAL] CVE-2019-3899 heketi: heketi can be installed using insecure defaults
CVE-2019-3899 heketi: heketi can be installed using insecure defaults
Heketi is used to manage GlusterFS nodes and volumes. The default configuration of Heketi does not require any authentication potentially exposing the management interface to misuse.
Discussion:
If configuring via the JSON above you also need to set "use_auth" to true.
This differs slightly if you are setting the keys via environment variables as using the env vars will automatically do the equivalent of setting "use_auth" to true.
---
Mitigation:
After installation of Heketi
1. configure user and admin key in /etc/heketi/heketi.json file
...
{
"_port_comment": "Heketi Server Port Number",
"port": "8080",
"_use_auth": "Enable JWT authorization. Please enable for deployment",
"use_auth": true,
"_jwt": "Private ke
2019-04-22
Published