cnvd - cnvd-2017-00368

cnvd-2017-00368

Vulnerability from cnvd

Title: SLURM Prolog安全绕过漏洞

Description:

Slurm是一套用于大型和小型Linux群集中的开源的和高度可扩展的集群管理和作业调度系统。

Slurm存在安全绕过漏洞。攻击者可利用该漏洞绕过安全限制执行未授权操作。

Severity: 高

Patch Name: SLURM Prolog安全绕过漏洞的补丁

Patch Description:

Slurm是一套用于大型和小型Linux群集中的开源的和高度可扩展的集群管理和作业调度系统。

Slurm存在安全绕过漏洞。攻击者可利用该漏洞绕过安全限制执行未授权操作。目前，供应商发布了安全公告及相关补丁信息，修复了此漏洞。

Formal description:

厂商已发布漏洞修复程序，请及时关注更新： https://www.schedmd.com/news.php?id=178

Reference: http://www.securityfocus.com/bid/95299

Impacted products

Name
['SchedMD Slurm <15.08.13', 'SchedMD Slurm 16.，<16.05.7', 'SchedMD Slurm 17.，<17.02.0-pre4']

Show details on source website

JSON

To clipboard

{
  "bids": {
    "bid": {
      "bidNumber": "95299"
    }
  },
  "cves": {
    "cve": {
      "cveNumber": "CVE-2016-10030"
    }
  },
  "description": "Slurm\u662f\u4e00\u5957\u7528\u4e8e\u5927\u578b\u548c\u5c0f\u578bLinux\u7fa4\u96c6\u4e2d\u7684\u5f00\u6e90\u7684\u548c\u9ad8\u5ea6\u53ef\u6269\u5c55\u7684\u96c6\u7fa4\u7ba1\u7406\u548c\u4f5c\u4e1a\u8c03\u5ea6\u7cfb\u7edf\u3002\r\n\r\nSlurm\u5b58\u5728\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7ed5\u8fc7\u5b89\u5168\u9650\u5236\u6267\u884c\u672a\u6388\u6743\u64cd\u4f5c\u3002",
  "discovererName": "SchedMD",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttps://www.schedmd.com/news.php?id=178",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2017-00368",
  "openTime": "2017-01-12",
  "patchDescription": "Slurm\u662f\u4e00\u5957\u7528\u4e8e\u5927\u578b\u548c\u5c0f\u578bLinux\u7fa4\u96c6\u4e2d\u7684\u5f00\u6e90\u7684\u548c\u9ad8\u5ea6\u53ef\u6269\u5c55\u7684\u96c6\u7fa4\u7ba1\u7406\u548c\u4f5c\u4e1a\u8c03\u5ea6\u7cfb\u7edf\u3002\r\n\r\nSlurm\u5b58\u5728\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u7ed5\u8fc7\u5b89\u5168\u9650\u5236\u6267\u884c\u672a\u6388\u6743\u64cd\u4f5c\u3002\u76ee\u524d\uff0c\u4f9b\u5e94\u5546\u53d1\u5e03\u4e86\u5b89\u5168\u516c\u544a\u53ca\u76f8\u5173\u8865\u4e01\u4fe1\u606f\uff0c\u4fee\u590d\u4e86\u6b64\u6f0f\u6d1e\u3002",
  "patchName": "SLURM Prolog\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": [
      "SchedMD Slurm \u003c15.08.13",
      "SchedMD Slurm 16.*\uff0c\u003c16.05.7",
      "SchedMD Slurm 17.*\uff0c\u003c17.02.0-pre4"
    ]
  },
  "referenceLink": "http://www.securityfocus.com/bid/95299",
  "serverity": "\u9ad8",
  "submitTime": "2017-01-09",
  "title": "SLURM Prolog\u5b89\u5168\u7ed5\u8fc7\u6f0f\u6d1e"
}

CVE-2016-10030 (GCVE-0-2016-10030)

Vulnerability from cvelistv5

Published

2017-01-05 11:00

Modified

2024-08-06 03:07

Severity ?

CWE

Summary

The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 17.02.0-pre4 has a vulnerability in how the slurmd daemon informs users of a Prolog failure on a compute node. That vulnerability could allow a user to assume control of an arbitrary file on the system. Any exploitation of this is dependent on the user being able to cause or anticipate the failure (non-zero return code) of a Prolog script that their job would run on. This issue affects all Slurm versions from 0.6.0 (September 2005) to present. Workarounds to prevent exploitation of this are to either disable your Prolog script, or modify it such that it always returns 0 ("success") and adjust it to set the node as down using scontrol instead of relying on the slurmd to handle that automatically. If you do not have a Prolog set you are unaffected by this issue.

References

▼	URL	Tags
	https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44120ee	x_refsource_CONFIRM
	http://www.securityfocus.com/bid/95299	vdb-entry, x_refsource_BID
	https://www.schedmd.com/news.php?id=178	x_refsource_CONFIRM

Impacted products

	Vendor	Product	Version
	n/a	n/a	Version: n/a

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-06T03:07:31.955Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44120ee"
          },
          {
            "name": "95299",
            "tags": [
              "vdb-entry",
              "x_refsource_BID",
              "x_transferred"
            ],
            "url": "http://www.securityfocus.com/bid/95299"
          },
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://www.schedmd.com/news.php?id=178"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "n/a",
          "vendor": "n/a",
          "versions": [
            {
              "status": "affected",
              "version": "n/a"
            }
          ]
        }
      ],
      "datePublic": "2017-01-05T00:00:00",
      "descriptions": [
        {
          "lang": "en",
          "value": "The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 17.02.0-pre4 has a vulnerability in how the slurmd daemon informs users of a Prolog failure on a compute node. That vulnerability could allow a user to assume control of an arbitrary file on the system. Any exploitation of this is dependent on the user being able to cause or anticipate the failure (non-zero return code) of a Prolog script that their job would run on. This issue affects all Slurm versions from 0.6.0 (September 2005) to present. Workarounds to prevent exploitation of this are to either disable your Prolog script, or modify it such that it always returns 0 (\"success\") and adjust it to set the node as down using scontrol instead of relying on the slurmd to handle that automatically. If you do not have a Prolog set you are unaffected by this issue."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "n/a",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2017-01-09T10:57:01",
        "orgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
        "shortName": "mitre"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44120ee"
        },
        {
          "name": "95299",
          "tags": [
            "vdb-entry",
            "x_refsource_BID"
          ],
          "url": "http://www.securityfocus.com/bid/95299"
        },
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://www.schedmd.com/news.php?id=178"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "cve@mitre.org",
          "ID": "CVE-2016-10030",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "n/a",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "n/a"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "n/a"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "The _prolog_error function in slurmd/req.c in Slurm before 15.08.13, 16.x before 16.05.7, and 17.x before 17.02.0-pre4 has a vulnerability in how the slurmd daemon informs users of a Prolog failure on a compute node. That vulnerability could allow a user to assume control of an arbitrary file on the system. Any exploitation of this is dependent on the user being able to cause or anticipate the failure (non-zero return code) of a Prolog script that their job would run on. This issue affects all Slurm versions from 0.6.0 (September 2005) to present. Workarounds to prevent exploitation of this are to either disable your Prolog script, or modify it such that it always returns 0 (\"success\") and adjust it to set the node as down using scontrol instead of relying on the slurmd to handle that automatically. If you do not have a Prolog set you are unaffected by this issue."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "n/a"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44120ee",
              "refsource": "CONFIRM",
              "url": "https://github.com/SchedMD/slurm/commit/92362a92fffe60187df61f99ab11c249d44120ee"
            },
            {
              "name": "95299",
              "refsource": "BID",
              "url": "http://www.securityfocus.com/bid/95299"
            },
            {
              "name": "https://www.schedmd.com/news.php?id=178",
              "refsource": "CONFIRM",
              "url": "https://www.schedmd.com/news.php?id=178"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "8254265b-2729-46b6-b9e3-3dfca2d5bfca",
    "assignerShortName": "mitre",
    "cveId": "CVE-2016-10030",
    "datePublished": "2017-01-05T11:00:00",
    "dateReserved": "2016-12-22T00:00:00",
    "dateUpdated": "2024-08-06T03:07:31.955Z",
    "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