github - ghsa-jjjw-r883-r73w

ghsa-jjjw-r883-r73w

Vulnerability from github

Published

2022-05-13 01:38

Modified

2022-05-13 01:38

Severity ?

5.3 (Medium) - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Details

When the device is configured to perform account lockout with a defined period of time, any unauthenticated user attempting to log in as root with an incorrect password can trigger a lockout of the root account. When an SRX Series device is in cluster mode, and a cluster sync or failover operation occurs, then there will be errors associated with synch or failover while the root account is locked out. Administrators can confirm if the root account is locked out via the following command root@device> show system login lockout user root User Lockout start Lockout end root 1995-01-01 01:00:01 PDT 1995-11-01 01:31:01 PDT Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D65 on SRX series; 12.3X48 prior to 12.3X48-D45 on SRX series; 15.1X49 prior to 15.1X49-D75 on SRX series.

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2017-10604"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-307"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2017-07-17T13:18:00Z",
    "severity": "MODERATE"
  },
  "details": "When the device is configured to perform account lockout with a defined period of time, any unauthenticated user attempting to log in as root with an incorrect password can trigger a lockout of the root account. When an SRX Series device is in cluster mode, and a cluster sync or failover operation occurs, then there will be errors associated with synch or failover while the root account is locked out. Administrators can confirm if the root account is locked out via the following command root@device\u003e show system login lockout user root User Lockout start Lockout end root 1995-01-01 01:00:01 PDT 1995-11-01 01:31:01 PDT Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D65 on SRX series; 12.3X48 prior to 12.3X48-D45 on SRX series; 15.1X49 prior to 15.1X49-D75 on SRX series.",
  "id": "GHSA-jjjw-r883-r73w",
  "modified": "2022-05-13T01:38:22Z",
  "published": "2022-05-13T01:38:22Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2017-10604"
    },
    {
      "type": "WEB",
      "url": "https://kb.juniper.net/JSA10806"
    },
    {
      "type": "WEB",
      "url": "http://www.securitytracker.com/id/1038886"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ]
}

cve-2017-10604

Vulnerability from cvelistv5

Published

2017-07-14 14:00

Modified

2024-09-16 18:13

Severity ?

5.3 (Medium) - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Summary

Junos OS: SRX Series: Cluster configuration sync failures occur if the root user account is locked out

References

▼	URL	Tags
	http://www.securitytracker.com/id/1038886	vdb-entry, x_refsource_SECTRACK
	https://kb.juniper.net/JSA10806	x_refsource_CONFIRM

Impacted products

Vendor

Product

Version

▼

Juniper Networks

Junos OS

Version: 12.1X46 prior to 12.1X46-D65
Version: 12.3X48 prior to 12.3X48-D45
Version: 15.1X49 prior to 15.1X49-D75

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T17:41:55.638Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "name": "1038886",
            "tags": [
              "vdb-entry",
              "x_refsource_SECTRACK",
              "x_transferred"
            ],
            "url": "http://www.securitytracker.com/id/1038886"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://kb.juniper.net/JSA10806"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "platforms": [
            "SRX series"
          ],
          "product": "Junos OS",
          "vendor": "Juniper Networks",
          "versions": [
            {
              "status": "affected",
              "version": "12.1X46 prior to 12.1X46-D65"
            },
            {
              "status": "affected",
              "version": "12.3X48 prior to 12.3X48-D45"
            },
            {
              "status": "affected",
              "version": "15.1X49 prior to 15.1X49-D75"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "value": "This issue only affects devices configured to perform account lockout with a defined period of time; e.g.:\n  set system services ssh root-login deny\n  set system login retry-options tries-before-disconnect 5\n  set system login retry-options minimum-time 30\n  set system login retry-options lockout-period 30"
        },
        {
          "lang": "en",
          "value": "The root lockout feature is working as expected. It is only a problem when an SRX Series device is in a cluster configuration mode."
        }
      ],
      "datePublic": "2017-07-12T00:00:00",
      "descriptions": [
        {
          "lang": "en",
          "value": "When the device is configured to perform account lockout with a defined period of time, any unauthenticated user attempting to log in as root with an incorrect password can trigger a lockout of the root account. When an SRX Series device is in cluster mode, and a cluster sync or failover operation occurs, then there will be errors associated with synch or failover while the root account is locked out. Administrators can confirm if the root account is locked out via the following command root@device\u003e show system login lockout user root User Lockout start Lockout end root 1995-01-01 01:00:01 PDT 1995-11-01 01:31:01 PDT Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D65 on SRX series; 12.3X48 prior to 12.3X48-D45 on SRX series; 15.1X49 prior to 15.1X49-D75 on SRX series."
        }
      ],
      "metrics": [
        {
          "cvssV3_0": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
            "version": "3.0"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "denial of service to high availability features",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-07-15T09:57:01",
        "orgId": "8cbe9d5a-a066-4c94-8978-4b15efeae968",
        "shortName": "juniper"
      },
      "references": [
        {
          "name": "1038886",
          "tags": [
            "vdb-entry",
            "x_refsource_SECTRACK"
          ],
          "url": "http://www.securitytracker.com/id/1038886"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://kb.juniper.net/JSA10806"
        }
      ],
      "title": "Junos OS: SRX Series: Cluster configuration sync failures occur if the root user account is locked out",
      "workarounds": [
        {
          "lang": "en",
          "value": "The lockout feature does not impact console access for the root account.  Administrators may login via console, and block the offending incoming traffic which is causing the root account from being locked out via SSH connection attempts to restore cluster sync services from erroring or failing.\n\nAdministrators may block the offending SSH traffic from an upstream device.\n\nUse access lists or firewall filters to limit access to the device only from trusted administrative hosts, networks and users."
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "sirt@juniper.net",
          "DATE_PUBLIC": "2017-07-12T09:00",
          "ID": "CVE-2017-10604",
          "STATE": "PUBLIC",
          "TITLE": "Junos OS: SRX Series: Cluster configuration sync failures occur if the root user account is locked out"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Junos OS",
                      "version": {
                        "version_data": [
                          {
                            "platform": "SRX series",
                            "version_value": "12.1X46 prior to 12.1X46-D65"
                          },
                          {
                            "platform": "SRX series",
                            "version_value": "12.3X48 prior to 12.3X48-D45"
                          },
                          {
                            "platform": "SRX series",
                            "version_value": "15.1X49 prior to 15.1X49-D75"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Juniper Networks"
              }
            ]
          }
        },
        "configuration": [
          {
            "lang": "en",
            "value": "This issue only affects devices configured to perform account lockout with a defined period of time; e.g.:\n  set system services ssh root-login deny\n  set system login retry-options tries-before-disconnect 5\n  set system login retry-options minimum-time 30\n  set system login retry-options lockout-period 30"
          },
          {
            "lang": "en",
            "value": "The root lockout feature is working as expected. It is only a problem when an SRX Series device is in a cluster configuration mode."
          }
        ],
        "credit": [],
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "When the device is configured to perform account lockout with a defined period of time, any unauthenticated user attempting to log in as root with an incorrect password can trigger a lockout of the root account. When an SRX Series device is in cluster mode, and a cluster sync or failover operation occurs, then there will be errors associated with synch or failover while the root account is locked out. Administrators can confirm if the root account is locked out via the following command root@device\u003e show system login lockout user root User Lockout start Lockout end root 1995-01-01 01:00:01 PDT 1995-11-01 01:31:01 PDT Affected releases are Juniper Networks Junos OS 12.1X46 prior to 12.1X46-D65 on SRX series; 12.3X48 prior to 12.3X48-D45 on SRX series; 15.1X49 prior to 15.1X49-D75 on SRX series."
            }
          ]
        },
        "exploit": "Juniper SIRT is not aware of any malicious exploitation of this vulnerability.",
        "impact": {
          "cvss": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 5.3,
            "baseSeverity": "MEDIUM",
            "confidentialityImpact": "NONE",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "UNCHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N",
            "version": "3.0"
          }
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "denial of service to high availability features"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "1038886",
              "refsource": "SECTRACK",
              "url": "http://www.securitytracker.com/id/1038886"
            },
            {
              "name": "https://kb.juniper.net/JSA10806",
              "refsource": "CONFIRM",
              "url": "https://kb.juniper.net/JSA10806"
            }
          ]
        },
        "solution": "The following software releases have been updated to resolve this specific issue: 12.1X46-D65, 12.3X48-D45, 15.1X49-D75, and all subsequent releases.\n\nNOTE: Future SRX-Series releases above 15.1X49 Top of Tree from Junos OS 17.2R1 onward have been proactively resolved.\n\nThis issue is being tracked as PR 1222250 and is visible on the Customer Support website.",
        "work_around": [
          {
            "lang": "en",
            "value": "The lockout feature does not impact console access for the root account.  Administrators may login via console, and block the offending incoming traffic which is causing the root account from being locked out via SSH connection attempts to restore cluster sync services from erroring or failing.\n\nAdministrators may block the offending SSH traffic from an upstream device.\n\nUse access lists or firewall filters to limit access to the device only from trusted administrative hosts, networks and users."
          }
        ]
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8cbe9d5a-a066-4c94-8978-4b15efeae968",
    "assignerShortName": "juniper",
    "cveId": "CVE-2017-10604",
    "datePublished": "2017-07-14T14:00:00Z",
    "dateReserved": "2017-06-28T00:00:00",
    "dateUpdated": "2024-09-16T18:13:37.173Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date

Nomenclature

Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
Confirmed: The vulnerability is confirmed from an analyst perspective.
Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
Patched: This vulnerability was successfully patched by the user reporting the sighting.
Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
Not confirmed: The user expresses doubt about the veracity of the vulnerability.
Not patched: This vulnerability was not successfully patched by the user reporting the sighting.

Action not permitted