{"containers": {"cna": {"affected": [{"product": "Apache Pulsar", "vendor": "Apache Software Foundation", "versions": [{"lessThanOrEqual": "2.8.0", "status": "affected", "version": "Apache Pulsar", "versionType": "custom"}]}], "descriptions": [{"lang": "en", "value": "In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user. The Admin API get-message-by-id requires the user to input a topic and a ledger id. The ledger id is a pointer to the data, and it is supposed to be a valid it for the topic. Authorisation controls are performed against the topic name and there is not proper validation the that ledger id is valid in the context of such ledger. So it may happen that the user is able to read from a ledger that contains data owned by another tenant. This issue affects Apache Pulsar Apache Pulsar version 2.8.0 and prior versions; Apache Pulsar version 2.7.3 and prior versions; Apache Pulsar version 2.6.4 and prior versions."}], "metrics": [{"other": {"content": {"other": "moderate"}, "type": "unknown"}}], "problemTypes": [{"descriptions": [{"cweId": "CWE-863", "description": "CWE-863 Incorrect Authorization", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "shortName": "apache", "dateUpdated": "2023-07-18T11:52:20.375Z"}, "references": [{"tags": ["x_refsource_MISC"], "url": "https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId"}, {"tags": ["x_refsource_MISC"], "url": "https://github.com/apache/pulsar/issues/11814"}, {"tags": ["x_refsource_MISC"], "url": "https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr"}], "source": {"defect": ["https://github.com/apache/pulsar/issues/11814"], "discovery": "UNKNOWN"}, "title": "Pulsar Admin API allows access to data from other tenants using getMessageById API", "workarounds": [{"lang": "en", "value": "If you are running Pulsar behind a proxy you can disable access to the REST API for the flawed API \n\n/admin/v2/non-persistent/{tenant}/{namespace}/{topic}/ledger/{ledgerId}/entry/{entryId}"}], "x_generator": {"engine": "Vulnogram 0.0.9"}, "x_legacyV4Record": {"CVE_data_meta": {"ASSIGNER": "security@apache.org", "ID": "CVE-2021-41571", "STATE": "PUBLIC", "TITLE": "Pulsar Admin API allows access to data from other tenants using getMessageById API"}, "affects": {"vendor": {"vendor_data": [{"product": {"product_data": [{"product_name": "Apache Pulsar", "version": {"version_data": [{"version_affected": "<=", "version_name": "Apache Pulsar", "version_value": "2.8.0"}, {"version_affected": "<=", "version_name": "Apache Pulsar", "version_value": "2.7.3 +1"}, {"version_affected": "<=", "version_name": "Apache Pulsar", "version_value": "2.6.4 +1"}]}}]}, "vendor_name": "Apache Software Foundation"}]}}, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": {"description_data": [{"lang": "eng", "value": "In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user. The Admin API get-message-by-id requires the user to input a topic and a ledger id. The ledger id is a pointer to the data, and it is supposed to be a valid it for the topic. Authorisation controls are performed against the topic name and there is not proper validation the that ledger id is valid in the context of such ledger. So it may happen that the user is able to read from a ledger that contains data owned by another tenant. This issue affects Apache Pulsar Apache Pulsar version 2.8.0 and prior versions; Apache Pulsar version 2.7.3 and prior versions; Apache Pulsar version 2.6.4 and prior versions."}]}, "generator": {"engine": "Vulnogram 0.0.9"}, "impact": [{"other": "moderate"}], "problemtype": {"problemtype_data": [{"description": [{"lang": "eng", "value": "CWE-863 Incorrect Authorization"}]}]}, "references": {"reference_data": [{"name": "https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId", "refsource": "MISC", "url": "https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId"}, {"name": "https://github.com/apache/pulsar/issues/11814", "refsource": "MISC", "url": "https://github.com/apache/pulsar/issues/11814"}, {"name": "https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr", "refsource": "MISC", "url": "https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr"}]}, "source": {"defect": ["https://github.com/apache/pulsar/issues/11814"], "discovery": "UNKNOWN"}, "work_around": [{"lang": "en", "value": "If you are running Pulsar behind a proxy you can disable access to the REST API for the flawed API \n\n/admin/v2/non-persistent/{tenant}/{namespace}/{topic}/ledger/{ledgerId}/entry/{entryId}"}]}}, "adp": [{"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-04T03:15:29.204Z"}, "title": "CVE Program Container", "references": [{"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://github.com/apache/pulsar/issues/11814"}, {"tags": ["x_refsource_MISC", "x_transferred"], "url": "https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr"}]}]}, "cveMetadata": {"assignerOrgId": "f0158376-9dc2-43b6-827c-5f631a4d8d09", "assignerShortName": "apache", "cveId": "CVE-2021-41571", "datePublished": "2022-02-01T12:40:53", "dateReserved": "2021-09-23T00:00:00", "dateUpdated": "2024-08-04T03:15:29.204Z", "state": "PUBLISHED"}, "dataType": "CVE_RECORD", "dataVersion": "5.1"}

{}

{"configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*", "matchCriteriaId": "E7316A0A-1852-4DD2-926A-06FEA7D1D2FA", "versionEndExcluding": "2.6.4", "versionStartIncluding": "2.6.0", "vulnerable": true}, {"criteria": "cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*", "matchCriteriaId": "66FA9B80-0C01-492B-83B1-728214C6C810", "versionEndExcluding": "2.7.3", "versionStartIncluding": "2.7.0", "vulnerable": true}, {"criteria": "cpe:2.3:a:apache:pulsar:2.8.0:*:*:*:*:*:*:*", "matchCriteriaId": "D500E36D-2790-4ADB-B635-04223242421B", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "descriptions": [{"lang": "en", "value": "In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user. The Admin API get-message-by-id requires the user to input a topic and a ledger id. The ledger id is a pointer to the data, and it is supposed to be a valid it for the topic. Authorisation controls are performed against the topic name and there is not proper validation the that ledger id is valid in the context of such ledger. So it may happen that the user is able to read from a ledger that contains data owned by another tenant. This issue affects Apache Pulsar Apache Pulsar version 2.8.0 and prior versions; Apache Pulsar version 2.7.3 and prior versions; Apache Pulsar version 2.6.4 and prior versions."}, {"lang": "es", "value": "En Apache Pulsar es posible acceder a datos de BookKeeper que no pertenecen a los temas accesibles por el usuario autenticado. La API de administraci\u00f3n get-message-by-id requiere que el usuario introduzca un tema y un ledger id. El identificador del libro mayor es un puntero a los datos, y supone que es v\u00e1lido para el tema. Los controles de autorizaci\u00f3n son llevados a cabo contra el nombre del tema y no se presenta una comprobaci\u00f3n apropiada de que el ID del libro mayor sea v\u00e1lido en el contexto de dicho libro mayor. Por lo tanto, puede ocurrir que el usuario sea capaz de leer de un libro mayor que contiene datos que pertenecen a otro inquilino. Este problema afecta a Apache Pulsar versiones 2.8.0 y anteriores; Apache Pulsar versiones 2.7.3 y anteriores; Apache Pulsar versiones 2.6.4 y anteriores"}], "id": "CVE-2021-41571", "lastModified": "2024-11-21T06:26:27.173", "metrics": {"cvssMetricV2": [{"acInsufInfo": false, "baseSeverity": "MEDIUM", "cvssData": {"accessComplexity": "LOW", "accessVector": "NETWORK", "authentication": "SINGLE", "availabilityImpact": "NONE", "baseScore": 4.0, "confidentialityImpact": "PARTIAL", "integrityImpact": "NONE", "vectorString": "AV:N/AC:L/Au:S/C:P/I:N/A:N", "version": "2.0"}, "exploitabilityScore": 8.0, "impactScore": 2.9, "obtainAllPrivilege": false, "obtainOtherPrivilege": false, "obtainUserPrivilege": false, "source": "nvd@nist.gov", "type": "Primary", "userInteractionRequired": false}], "cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "NONE", "baseScore": 6.5, "baseSeverity": "MEDIUM", "confidentialityImpact": "HIGH", "integrityImpact": "NONE", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "version": "3.1"}, "exploitabilityScore": 2.8, "impactScore": 3.6, "source": "nvd@nist.gov", "type": "Primary"}]}, "published": "2022-02-01T13:15:09.663", "references": [{"source": "security@apache.org", "tags": ["Exploit", "Issue Tracking", "Patch", "Third Party Advisory"], "url": "https://github.com/apache/pulsar/issues/11814"}, {"source": "security@apache.org", "tags": ["Mailing List", "Vendor Advisory"], "url": "https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr"}, {"source": "security@apache.org", "tags": ["Patch", "Vendor Advisory"], "url": "https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Exploit", "Issue Tracking", "Patch", "Third Party Advisory"], "url": "https://github.com/apache/pulsar/issues/11814"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Mailing List", "Vendor Advisory"], "url": "https://lists.apache.org/thread/8n3k7pvyh4cf9q2jfzb6pb32ync6xlvr"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Patch", "Vendor Advisory"], "url": "https://pulsar.apache.org/admin-rest-api/#operation/getLastMessageId"}], "sourceIdentifier": "security@apache.org", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-863"}], "source": "security@apache.org", "type": "Secondary"}, {"description": [{"lang": "en", "value": "CWE-863"}], "source": "nvd@nist.gov", "type": "Secondary"}]}

{"bugzilla": {"description": "pulsar: Pulsar Admin API allows access to data from other tenants using getMessageById API", "id": "2048682", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2048682"}, "csaw": false, "cvss3": {"cvss3_base_score": "6.5", "cvss3_scoring_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N", "status": "draft"}, "cwe": "CWE-863->CWE-1220", "details": ["In Apache Pulsar it is possible to access data from BookKeeper that does not belong to the topics accessible by the authenticated user. The Admin API get-message-by-id requires the user to input a topic and a ledger id. The ledger id is a pointer to the data, and it is supposed to be a valid it for the topic. Authorisation controls are performed against the topic name and there is not proper validation the that ledger id is valid in the context of such ledger. So it may happen that the user is able to read from a ledger that contains data owned by another tenant. This issue affects Apache Pulsar Apache Pulsar version 2.8.0 and prior versions; Apache Pulsar version 2.7.3 and prior versions; Apache Pulsar version 2.6.4 and prior versions."], "name": "CVE-2021-41571", "package_state": [{"cpe": "cpe:/a:redhat:integration:1", "fix_state": "Affected", "package_name": "pulsar-client-admin", "product_name": "Red Hat Integration Camel K"}], "public_date": "2022-01-31T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2021-41571\nhttps://nvd.nist.gov/vuln/detail/CVE-2021-41571"], "threat_severity": "Moderate"}