A vulnerability was found in ipa before 4.4. IdM's ca-del, ca-disable, and ca-enable commands did not properly check the user's permissions while modifying CAs in Dogtag. An authenticated, unauthorized attacker could use this flaw to delete, disable, or enable CAs causing various denial of service problems with certificate issuance, OCSP signing, and deletion of secret keys.

The remote MiracleLinux 7 host has packages installed that are affected by a vulnerability as referenced in the AXSA:2017-1334:03 advisory.

    IPA is an integrated solution to provide centrally managed Identity (users,     hosts, services), Authentication (SSO, 2FA), and Authorization     (host access control, SELinux user roles, services). The solution provides     features for further integration with Linux based clients (SUDO, automount)     and integration with Active Directory based infrastructures (Trusts).
    Security issues fixed with this release:
    CVE-2017-2590
    ** RESERVED **     This candidate has been reserved by an organization or individual that     will use it when announcing a new security problem.  When the     candidate has been publicized, the details for this candidate will be     provided.
    Fixed bugs:
    * Previously, during an Identity Management (IdM) replica installation that runs on domain level 1 or     higher, Directory Server was not configured to use TLS encryption. As a consequence, installing a     certificate authority (CA) on that replica failed. Directory Server is now configured to use TLS     encryption during the replica installation and as a result, the CA installation works as expected.
    * Previously, the Identity Management (IdM) public key infrastructure (PKI) component was configured to     listen on the ::1 IPv6 localhost address. In environments have the the IPv6 protocol disabled, the     replica installer was unable to retrieve the Directory Server certificate, and the installation failed.
    The default listening address of the PKI connector has been updated from the IP address to localhost. As     a result, the PKI connector now listens on the correct addresses in IPv4 and IPv6 environments.
    * Previously, when installing a certificate authority (CA) on a replica, Identity Management (IdM) was     unable to provide third-party CA certificates to the Certificate System CA installer. As a consequence,     the installer was unable to connect to the remote master if the remote master used a third-party server     certificate, and the installation failed. This updates applies a patch and as a result, installing a CA     replica works as expected in the described situation.
    * When installing a replica, the web server service entry is created on the Identity Management (IdM)     master and replicated to all IdM servers. Previously, when installing a replica without a certificate     authority (CA), in certain situations the service entry was not replicated to the new replica on time, and     the installation failed. The replica installer has been updated and now waits until the web server service     entry is replicated. As a result, the replica installation no longer fails in the described situation.

Tenable has extracted the preceding description block directly from the MiracleLinux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

An update for ipa is now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat Identity Management (IdM) is a centralized authentication, identity management, and authorization solution for both traditional and cloud-based enterprise environments.

Security Fix(es) :

* It was found that IdM's ca-del, ca-disable, and ca-enable commands did not properly check the user's permissions while modifying CAs in Dogtag. An authenticated, unauthorized attacker could use this flaw to delete, disable, or enable CAs causing various denial of service problems with certificate issuance, OCSP signing, and deletion of secret keys. (CVE-2017-2590)

This issue was discovered by Fraser Tweedale (Red Hat).

Bug Fix(es) :

* Previously, during an Identity Management (IdM) replica installation that runs on domain level '1' or higher, Directory Server was not configured to use TLS encryption. As a consequence, installing a certificate authority (CA) on that replica failed. Directory Server is now configured to use TLS encryption during the replica installation and as a result, the CA installation works as expected. (BZ#1410760)

* Previously, the Identity Management (IdM) public key infrastructure (PKI) component was configured to listen on the '::1' IPv6 localhost address. In environments have the the IPv6 protocol disabled, the replica installer was unable to retrieve the Directory Server certificate, and the installation failed. The default listening address of the PKI connector has been updated from the IP address to 'localhost'. As a result, the PKI connector now listens on the correct addresses in IPv4 and IPv6 environments. (BZ# 1416481)

* Previously, when installing a certificate authority (CA) on a replica, Identity Management (IdM) was unable to provide third-party CA certificates to the Certificate System CA installer. As a consequence, the installer was unable to connect to the remote master if the remote master used a third-party server certificate, and the installation failed. This updates applies a patch and as a result, installing a CA replica works as expected in the described situation.
(BZ#1415158)

* When installing a replica, the web server service entry is created on the Identity Management (IdM) master and replicated to all IdM servers. Previously, when installing a replica without a certificate authority (CA), in certain situations the service entry was not replicated to the new replica on time, and the installation failed.
The replica installer has been updated and now waits until the web server service entry is replicated. As a result, the replica installation no longer fails in the described situation. (BZ#1416488)

Note that Tenable Network Security has attempted to extract the preceding description block directly from the corresponding Red Hat security advisory. Virtuozzo provides no description for VZLSA advisories. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Fixed CVE 2017-2590: freeipa: ipa: Insufficient permission check for ca-del, ca-disable and ca-enable commands [fedora-all]

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

An update for ipa is now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

Red Hat Identity Management (IdM) is a centralized authentication, identity management, and authorization solution for both traditional and cloud-based enterprise environments.

Security Fix(es) :

* It was found that IdM's ca-del, ca-disable, and ca-enable commands did not properly check the user's permissions while modifying CAs in Dogtag. An authenticated, unauthorized attacker could use this flaw to delete, disable, or enable CAs causing various denial of service problems with certificate issuance, OCSP signing, and deletion of secret keys. (CVE-2017-2590)

This issue was discovered by Fraser Tweedale (Red Hat).

Bug Fix(es) :

* Previously, during an Identity Management (IdM) replica installation that runs on domain level '1' or higher, Directory Server was not configured to use TLS encryption. As a consequence, installing a certificate authority (CA) on that replica failed. Directory Server is now configured to use TLS encryption during the replica installation and as a result, the CA installation works as expected. (BZ#1410760)

* Previously, the Identity Management (IdM) public key infrastructure (PKI) component was configured to listen on the '::1' IPv6 localhost address. In environments have the the IPv6 protocol disabled, the replica installer was unable to retrieve the Directory Server certificate, and the installation failed. The default listening address of the PKI connector has been updated from the IP address to 'localhost'. As a result, the PKI connector now listens on the correct addresses in IPv4 and IPv6 environments. (BZ# 1416481)

* Previously, when installing a certificate authority (CA) on a replica, Identity Management (IdM) was unable to provide third-party CA certificates to the Certificate System CA installer. As a consequence, the installer was unable to connect to the remote master if the remote master used a third-party server certificate, and the installation failed. This updates applies a patch and as a result, installing a CA replica works as expected in the described situation.
(BZ#1415158)

* When installing a replica, the web server service entry is created on the Identity Management (IdM) master and replicated to all IdM servers. Previously, when installing a replica without a certificate authority (CA), in certain situations the service entry was not replicated to the new replica on time, and the installation failed.
The replica installer has been updated and now waits until the web server service entry is replicated. As a result, the replica installation no longer fails in the described situation. (BZ#1416488)

Security Fix(es) :

  - It was found that IdM's ca-del, ca-disable, and     ca-enable commands did not properly check the user's     permissions while modifying CAs in Dogtag. An     authenticated, unauthorized attacker could use this flaw     to delete, disable, or enable CAs causing various denial     of service problems with certificate issuance, OCSP     signing, and deletion of secret keys. (CVE-2017-2590)

Bug Fix(es) :

  - Previously, during an Identity Management (IdM) replica     installation that runs on domain level '1' or higher,     Directory Server was not configured to use TLS     encryption. As a consequence, installing a certificate     authority (CA) on that replica failed. Directory Server     is now configured to use TLS encryption during the     replica installation and as a result, the CA     installation works as expected.

  - Previously, the Identity Management (IdM) public key     infrastructure (PKI) component was configured to listen     on the '::1' IPv6 localhost address. In environments     have the the IPv6 protocol disabled, the replica     installer was unable to retrieve the Directory Server     certificate, and the installation failed. The default     listening address of the PKI connector has been updated     from the IP address to 'localhost'. As a result, the PKI     connector now listens on the correct addresses in IPv4     and IPv6 environments.

  - Previously, when installing a certificate authority (CA)     on a replica, Identity Management (IdM) was unable to     provide third-party CA certificates to the Certificate     System CA installer. As a consequence, the installer was     unable to connect to the remote master if the remote     master used a third-party server certificate, and the     installation failed. This updates applies a patch and as     a result, installing a CA replica works as expected in     the described situation.

  - When installing a replica, the web server service entry     is created on the Identity Management (IdM) master and     replicated to all IdM servers. Previously, when     installing a replica without a certificate authority     (CA), in certain situations the service entry was not     replicated to the new replica on time, and the     installation failed. The replica installer has been     updated and now waits until the web server service entry     is replicated. As a result, the replica installation no     longer fails in the described situation.

The remote Oracle Linux 7 host has packages installed that are affected by a vulnerability as referenced in the ELSA-2017-0388 advisory.

    - Resolves: #1413137 CVE-2017-2590 ipa: Insufficient permission check for       ca-del, ca-disable and ca-enable commands
      - ca: correctly authorise ca-del, ca-enable and ca-disable

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
289914	MiracleLinux 7 : ipa-4.4.0-14.6.0.1.el7.AXS7 (AXSA:2017-1334:03)	Nessus	Miracle Linux Local Security Checks	high
101432	Virtuozzo 7 : ipa-admintools / ipa-client / ipa-client-common / etc (VZLSA-2017-0388)	Nessus	Virtuozzo Local Security Checks	high
97618	Fedora 25 : freeipa (2017-98f85533f0)	Nessus	Fedora Local Security Checks	high
97527	CentOS 7 : ipa (CESA-2017:0388)	Nessus	CentOS Local Security Checks	high
97515	Scientific Linux Security Update : ipa on SL7.x x86_64 (20170302)	Nessus	Scientific Linux Local Security Checks	high
97511	RHEL 7 : ipa (RHSA-2017:0388)	Nessus	Red Hat Local Security Checks	high
97507	Oracle Linux 7 : ipa (ELSA-2017-0388)	Nessus	Oracle Linux Local Security Checks	high

Detections

Analytics

CVE-2017-2590

high

Tenable Plugins

high

high

high

high

high

high

high