Vulnerability-Lookup

CNVD-2022-14707

Vulnerability from cnvd - Published: 2022-02-23

Title

Apache Karaf代码问题漏洞（CNVD-2022-14707）

Description

Apache Karaf是美国阿帕奇（Apache）基金会的一款用于部署应用程序和组件的轻量级的OSGi（Java动态化模块化系统）容器。 Apache Karaf存在代码问题漏洞，该漏洞源于在处理序列化数据时输入验证不安全，远程攻击者可利用该漏洞可以将专门制作的数据传递给应用程序，并在目标系统上执行任意代码。

Severity

中

Patch Name

Apache Karaf代码问题漏洞（CNVD-2022-14707）的补丁

Patch Description

Formal description

厂商已发布了漏洞修复程序，请及时关注更新： http://issues.apache.org/jira/browse/KARAF-7312

Reference

https://www.cybersecurity-help.cz/vdb/SB2022012521

Impacted products

Name
Apache Karaf <4.3.6

Show details on source website

JSON

To clipboard

{
  "cves": {
    "cve": {
      "cveNumber": "CVE-2021-41766",
      "cveUrl": "https://nvd.nist.gov/vuln/detail/CVE-2021-41766"
    }
  },
  "description": "Apache Karaf\u662f\u7f8e\u56fd\u963f\u5e15\u5947\uff08Apache\uff09\u57fa\u91d1\u4f1a\u7684\u4e00\u6b3e\u7528\u4e8e\u90e8\u7f72\u5e94\u7528\u7a0b\u5e8f\u548c\u7ec4\u4ef6\u7684\u8f7b\u91cf\u7ea7\u7684OSGi\uff08Java\u52a8\u6001\u5316\u6a21\u5757\u5316\u7cfb\u7edf\uff09\u5bb9\u5668\u3002\n\nApache Karaf\u5b58\u5728\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u5728\u5904\u7406\u5e8f\u5217\u5316\u6570\u636e\u65f6\u8f93\u5165\u9a8c\u8bc1\u4e0d\u5b89\u5168\uff0c\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u53ef\u4ee5\u5c06\u4e13\u95e8\u5236\u4f5c\u7684\u6570\u636e\u4f20\u9012\u7ed9\u5e94\u7528\u7a0b\u5e8f\uff0c\u5e76\u5728\u76ee\u6807\u7cfb\u7edf\u4e0a\u6267\u884c\u4efb\u610f\u4ee3\u7801\u3002",
  "formalWay": "\u5382\u5546\u5df2\u53d1\u5e03\u4e86\u6f0f\u6d1e\u4fee\u590d\u7a0b\u5e8f\uff0c\u8bf7\u53ca\u65f6\u5173\u6ce8\u66f4\u65b0\uff1a\r\nhttp://issues.apache.org/jira/browse/KARAF-7312",
  "isEvent": "\u901a\u7528\u8f6f\u786c\u4ef6\u6f0f\u6d1e",
  "number": "CNVD-2022-14707",
  "openTime": "2022-02-23",
  "patchDescription": "Apache Karaf\u662f\u7f8e\u56fd\u963f\u5e15\u5947\uff08Apache\uff09\u57fa\u91d1\u4f1a\u7684\u4e00\u6b3e\u7528\u4e8e\u90e8\u7f72\u5e94\u7528\u7a0b\u5e8f\u548c\u7ec4\u4ef6\u7684\u8f7b\u91cf\u7ea7\u7684OSGi\uff08Java\u52a8\u6001\u5316\u6a21\u5757\u5316\u7cfb\u7edf\uff09\u5bb9\u5668\u3002\r\n\r\nApache Karaf\u5b58\u5728\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\uff0c\u8be5\u6f0f\u6d1e\u6e90\u4e8e\u5728\u5904\u7406\u5e8f\u5217\u5316\u6570\u636e\u65f6\u8f93\u5165\u9a8c\u8bc1\u4e0d\u5b89\u5168\uff0c\u8fdc\u7a0b\u653b\u51fb\u8005\u53ef\u5229\u7528\u8be5\u6f0f\u6d1e\u53ef\u4ee5\u5c06\u4e13\u95e8\u5236\u4f5c\u7684\u6570\u636e\u4f20\u9012\u7ed9\u5e94\u7528\u7a0b\u5e8f\uff0c\u5e76\u5728\u76ee\u6807\u7cfb\u7edf\u4e0a\u6267\u884c\u4efb\u610f\u4ee3\u7801\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": "Apache Karaf\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\uff08CNVD-2022-14707\uff09\u7684\u8865\u4e01",
  "products": {
    "product": "Apache Karaf \u003c4.3.6"
  },
  "referenceLink": "https://www.cybersecurity-help.cz/vdb/SB2022012521",
  "serverity": "\u4e2d",
  "submitTime": "2022-01-27",
  "title": "Apache Karaf\u4ee3\u7801\u95ee\u9898\u6f0f\u6d1e\uff08CNVD-2022-14707\uff09"
}

CVE-2021-41766 (GCVE-0-2021-41766)

Vulnerability from cvelistv5 – Published: 2022-01-26 11:10 – Updated: 2024-08-04 03:15

Title

Insecure Java Deserialization in Apache Karaf

Summary

Apache Karaf allows monitoring of applications and the Java runtime by using the Java Management Extensions (JMX). JMX is a Java RMI based technology that relies on Java serialized objects for client server communication. Whereas the default JMX implementation is hardened against unauthenticated deserialization attacks, the implementation used by Apache Karaf is not protected against this kind of attack. The impact of Java deserialization vulnerabilities strongly depends on the classes that are available within the targets class path. Generally speaking, deserialization of untrusted data does always represent a high security risk and should be prevented. The risk is low as, by default, Karaf uses a limited set of classes in the JMX server class path. It depends of system scoped classes (e.g. jar in the lib folder).

Severity

No CVSS data available.

CWE

Insecure Java Deserialization

Assigner

apache mitre root

References

1 reference

URL	Tags
https://karaf.apache.org/security/cve-2021-41766.txt	x_refsource_MISC

Impacted products

1 product

Vendor	Product	Version
Apache Software Foundation	Apache Karaf	Affected: Apache Karaf , < 4.3.6 (custom)

Credits

This issue was reported by Daniel Heyne, Konstantin Samuel and Tobias Neitzel.

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T03:15:29.312Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_refsource_MISC",
              "x_transferred"
            ],
            "url": "https://karaf.apache.org/security/cve-2021-41766.txt"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "product": "Apache Karaf",
          "vendor": "Apache Software Foundation",
          "versions": [
            {
              "lessThan": "4.3.6",
              "status": "affected",
              "version": "Apache Karaf",
              "versionType": "custom"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "value": "This issue was reported by Daniel Heyne, Konstantin Samuel and Tobias Neitzel."
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "Apache Karaf allows monitoring of applications and the Java runtime by using the Java Management Extensions (JMX). JMX is a Java RMI based technology that relies on Java serialized objects for client server communication. Whereas the default JMX implementation is hardened against unauthenticated deserialization attacks, the implementation used by Apache Karaf is not protected against this kind of attack. The impact of Java deserialization vulnerabilities strongly depends on the classes that are available within the targets class path. Generally speaking, deserialization of untrusted data does always represent a high security risk and should be prevented. The risk is low as, by default, Karaf uses a limited set of classes in the JMX server class path. It depends of system scoped classes (e.g. jar in the lib folder)."
        }
      ],
      "metrics": [
        {
          "other": {
            "content": {
              "other": "The risk is low as, by default, Karaf uses a limited set of classes in the JMX server class path. It depends of system scoped classes (e.g. jar in the lib folder)."
            },
            "type": "unknown"
          }
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "description": "Insecure Java Deserialization",
              "lang": "en",
              "type": "text"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2022-01-26T11:10:11.000Z",
        "orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
        "shortName": "apache"
      },
      "references": [
        {
          "tags": [
            "x_refsource_MISC"
          ],
          "url": "https://karaf.apache.org/security/cve-2021-41766.txt"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Insecure Java Deserialization in Apache Karaf",
      "workarounds": [
        {
          "lang": "en",
          "value": "Apache Karaf users should upgrade to 4.3.6 or later as soon as possible, or disable remote access to JMX server."
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 0.0.9"
      },
      "x_legacyV4Record": {
        "CVE_data_meta": {
          "ASSIGNER": "security@apache.org",
          "ID": "CVE-2021-41766",
          "STATE": "PUBLIC",
          "TITLE": "Insecure Java Deserialization in Apache Karaf"
        },
        "affects": {
          "vendor": {
            "vendor_data": [
              {
                "product": {
                  "product_data": [
                    {
                      "product_name": "Apache Karaf",
                      "version": {
                        "version_data": [
                          {
                            "version_affected": "\u003c",
                            "version_name": "Apache Karaf",
                            "version_value": "4.3.6"
                          }
                        ]
                      }
                    }
                  ]
                },
                "vendor_name": "Apache Software Foundation"
              }
            ]
          }
        },
        "credit": [
          {
            "lang": "eng",
            "value": "This issue was reported by Daniel Heyne, Konstantin Samuel and Tobias Neitzel."
          }
        ],
        "data_format": "MITRE",
        "data_type": "CVE",
        "data_version": "4.0",
        "description": {
          "description_data": [
            {
              "lang": "eng",
              "value": "Apache Karaf allows monitoring of applications and the Java runtime by using the Java Management Extensions (JMX). JMX is a Java RMI based technology that relies on Java serialized objects for client server communication. Whereas the default JMX implementation is hardened against unauthenticated deserialization attacks, the implementation used by Apache Karaf is not protected against this kind of attack. The impact of Java deserialization vulnerabilities strongly depends on the classes that are available within the targets class path. Generally speaking, deserialization of untrusted data does always represent a high security risk and should be prevented. The risk is low as, by default, Karaf uses a limited set of classes in the JMX server class path. It depends of system scoped classes (e.g. jar in the lib folder)."
            }
          ]
        },
        "generator": {
          "engine": "Vulnogram 0.0.9"
        },
        "impact": [
          {
            "other": "The risk is low as, by default, Karaf uses a limited set of classes in the JMX server class path. It depends of system scoped classes (e.g. jar in the lib folder)."
          }
        ],
        "problemtype": {
          "problemtype_data": [
            {
              "description": [
                {
                  "lang": "eng",
                  "value": "Insecure Java Deserialization"
                }
              ]
            }
          ]
        },
        "references": {
          "reference_data": [
            {
              "name": "https://karaf.apache.org/security/cve-2021-41766.txt",
              "refsource": "MISC",
              "url": "https://karaf.apache.org/security/cve-2021-41766.txt"
            }
          ]
        },
        "source": {
          "discovery": "UNKNOWN"
        },
        "work_around": [
          {
            "lang": "en",
            "value": "Apache Karaf users should upgrade to 4.3.6 or later as soon as possible, or disable remote access to JMX server."
          }
        ]
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09",
    "assignerShortName": "apache",
    "cveId": "CVE-2021-41766",
    "datePublished": "2022-01-26T11:10:11.000Z",
    "dateReserved": "2021-09-27T00:00:00.000Z",
    "dateUpdated": "2024-08-04T03:15:29.312Z",
    "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.

Detection rules are retrieved from Rulezet.

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.