Vulnerability-Lookup

CNVD-2018-05228

Vulnerability from cnvd - Published: 2018-03-14

Title

Atlassian Crowd crowd-application插件模块用户伪造漏洞

Description

Atlassian Crowd是澳大利亚Atlassian公司的一套基于Web的单点登录系统。该系统为多用户、网络应用程序和目录服务器提供验证、授权等功能。crowd-application plugin module是其中的一个SSO管理插件。 Atlassian Crowd 1.5.0版本至3.1.2版本（不包括3.1.2版本）中的crowd-application插件模块存在安全漏洞。攻击者可利用该漏洞在REST请求中伪造Crowd用户。

Severity

中

Patch Name

Atlassian Crowd crowd-application插件模块用户伪造漏洞的补丁

Patch Description

Formal description

目前厂商已发布升级补丁以修复漏洞，补丁获取链接： https://jira.atlassian.com/browse/CWD-5009

Reference

https://jira.atlassian.com/browse/CWD-5009

Impacted products

Name
Atlassian Crowd >=1.5.0，<=3.1.2

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2017-16858",
      "cveUrl": "http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16858"
    }
  },
  "description": "Atlassian Crowd\u662f\u6fb3\u5927\u5229\u4e9aAtlassian\u516c\u53f8\u7684\u4e00\u5957\u57fa\u4e8eWeb\u7684\u5355\u70b9\u767b\u5f55\u7cfb\u7edf\u3002\u8be5\u7cfb\u7edf\u4e3a\u591a\u7528\u6237\u3001\u7f51\u7edc\u5e94\u7528\u7a0b\u5e8f\u548c\u76ee\u5f55\u670d\u52a1\u5668\u63d0\u4f9b\u9a8c\u8bc1\u3001\u6388\u6743\u7b49\u529f\u80fd\u3002crowd-application plugin module\u662f\u5176\u4e2d\u7684\u4e00\u4e2aSSO\u7ba1\u7406\u63d2\u4ef6\u3002\r\n\r\nAtlassian Crowd 1.5.0\u7248\u672c\u81f33.1.2\u7248\u672c\uff08\u4e0d\u5305\u62ec3.1.2\u7248\u672c\uff09\u4e2d\u7684crowd-application\u63d2\u4ef6\u6a21\u5757\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5728REST\u8bf7\u6c42\u4e2d\u4f2a\u9020Crowd\u7528\u6237\u3002",
  "discovererName": "Patryk Petrowski",
  "formalWay": "\u76ee\u524d\u5382\u5546\u5df2\u53d1\u5e03\u5347\u7ea7\u8865\u4e01\u4ee5\u4fee\u590d\u6f0f\u6d1e\uff0c\u8865\u4e01\u83b7\u53d6\u94fe\u63a5\uff1a\r\nhttps://jira.atlassian.com/browse/CWD-5009",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2018-05228",
  "openTime": "2018-03-14",
  "patchDescription": "Atlassian Crowd\u662f\u6fb3\u5927\u5229\u4e9aAtlassian\u516c\u53f8\u7684\u4e00\u5957\u57fa\u4e8eWeb\u7684\u5355\u70b9\u767b\u5f55\u7cfb\u7edf\u3002\u8be5\u7cfb\u7edf\u4e3a\u591a\u7528\u6237\u3001\u7f51\u7edc\u5e94\u7528\u7a0b\u5e8f\u548c\u76ee\u5f55\u670d\u52a1\u5668\u63d0\u4f9b\u9a8c\u8bc1\u3001\u6388\u6743\u7b49\u529f\u80fd\u3002crowd-application plugin module\u662f\u5176\u4e2d\u7684\u4e00\u4e2aSSO\u7ba1\u7406\u63d2\u4ef6\u3002\r\n\r\nAtlassian Crowd 1.5.0\u7248\u672c\u81f33.1.2\u7248\u672c\uff08\u4e0d\u5305\u62ec3.1.2\u7248\u672c\uff09\u4e2d\u7684crowd-application\u63d2\u4ef6\u6a21\u5757\u5b58\u5728\u5b89\u5168\u6f0f\u6d1e\u3002\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u5728REST\u8bf7\u6c42\u4e2d\u4f2a\u9020Crowd\u7528\u6237\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": "Atlassian Crowd crowd-application\u63d2\u4ef6\u6a21\u5757\u7528\u6237\u4f2a\u9020\u6f0f\u6d1e\u7684\u8865\u4e01",
  "products": {
    "product": "Atlassian Crowd \u003e=1.5.0\uff0c\u003c=3.1.2"
  },
  "referenceLink": "https://jira.atlassian.com/browse/CWD-5009",
  "serverity": "\u4e2d",
  "submitTime": "2018-02-06",
  "title": "Atlassian Crowd crowd-application\u63d2\u4ef6\u6a21\u5757\u7528\u6237\u4f2a\u9020\u6f0f\u6d1e"
}

CVE-2017-16858 (GCVE-0-2017-16858)

Vulnerability from cvelistv5 – Published: 2018-01-31 14:00 – Updated: 2024-09-17 00:40

Summary

The 'crowd-application' plugin module (notably used by the Google Apps plugin) in Atlassian Crowd from version 1.5.0 before version 3.1.2 allowed an attacker to impersonate a Crowd user in REST requests by being able to authenticate to a directory bound to an application using the feature. Given the following situation: the Crowd application is bound to directory 1 and has a user called admin and the Google Apps application is bound to directory 2, which also has a user called admin, it was possible to authenticate REST requests using the credentials of the user coming from directory 2 and impersonate the user from directory 1.

Severity

No CVSS data available.

CWE

CWE-863 - Incorrect Authorization (CWE-863)

Assigner

atlassian mitre root Scorecard

References

1 reference

URL	Tags
https://jira.atlassian.com/browse/CWD-5009	x_refsource_CONFIRM

Impacted products

1 product

Vendor	Product	Version
Atlassian	Crowd	Affected: from 1.5.0 before 3.1.2

Date Public

2018-01-30 00:00

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-05T20:35:21.278Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_CONFIRM",
              "x_transferred"
            ],
            "url": "https://jira.atlassian.com/browse/CWD-5009"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Crowd",
          "vendor": "Atlassian",
          "versions": [
            {
              "status": "affected",
              "version": "from 1.5.0 before 3.1.2"
            }
          ]
        }
      ],
      "datePublic": "2018-01-30T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "The \u0027crowd-application\u0027 plugin module (notably used by the Google Apps plugin) in Atlassian Crowd from version 1.5.0 before version 3.1.2 allowed an attacker to impersonate a Crowd user in REST requests by being able to authenticate to a directory bound to an application using the feature. Given the following situation: the Crowd application is bound to directory 1 and has a user called admin and the Google Apps application is bound to directory 2, which also has a user called admin, it was possible to authenticate REST requests using the credentials of the user coming from directory 2 and impersonate the user from directory 1."
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-863",
              "description": "Incorrect Authorization (CWE-863)",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2018-01-31T13:57:01.000Z",
        "orgId": "f08a6ab8-ed46-4c22-8884-d911ccfe3c66",
        "shortName": "atlassian"
      },
      "references": [
        {
          "tags": [
            "x_refsource_CONFIRM"
          ],
          "url": "https://jira.atlassian.com/browse/CWD-5009"
        }
      ],
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security@atlassian.com",
          "DATE_PUBLIC": "2018-01-30T00:00:00",
          "ID": "CVE-2017-16858",
          "STATE": "PUBLIC"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Crowd",
                      "version": {
                        "version_data": [
                          {
                            "version_value": "from 1.5.0 before 3.1.2"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Atlassian"
              }
            ]
          }
        },
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "The \u0027crowd-application\u0027 plugin module (notably used by the Google Apps plugin) in Atlassian Crowd from version 1.5.0 before version 3.1.2 allowed an attacker to impersonate a Crowd user in REST requests by being able to authenticate to a directory bound to an application using the feature. Given the following situation: the Crowd application is bound to directory 1 and has a user called admin and the Google Apps application is bound to directory 2, which also has a user called admin, it was possible to authenticate REST requests using the credentials of the user coming from directory 2 and impersonate the user from directory 1."
            }
          ]
        },
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "Incorrect Authorization (CWE-863)"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://jira.atlassian.com/browse/CWD-5009",
              "refsource": "CONFIRM",
              "url": "https://jira.atlassian.com/browse/CWD-5009"
            }
          ]
        }
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f08a6ab8-ed46-4c22-8884-d911ccfe3c66",
    "assignerShortName": "atlassian",
    "cveId": "CVE-2017-16858",
    "datePublished": "2018-01-31T14:00:00.000Z",
    "dateReserved": "2017-11-16T00:00:00.000Z",
    "dateUpdated": "2024-09-17T00:40:54.506Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1"
}

Sightings

Author	Source	Type	Date	Other

Nomenclature

Seen: The vulnerability was mentioned, discussed, or observed by the user.
Confirmed: The vulnerability has been validated from an analyst's perspective.
Published Proof of Concept: A public proof of concept is available for this vulnerability.
Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
Not confirmed: The user expressed doubt about the validity of the vulnerability.
Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base model, served locally by ML-Gateway. They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.

Action not permitted

CNVD-2018-05228

CVE-2017-16858 (GCVE-0-2017-16858)

Tags

Sightings

Nomenclature

Related by attack behaviour