FKIE_CVE-2022-33684
Vulnerability from fkie_nvd - Published: 2022-11-04 12:15 - Updated: 2026-06-17 04:498.1 (High) - CVSS:3.1/
| URL | Tags | ||
|---|---|---|---|
| security@apache.org | https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566f | Exploit, Issue Tracking, Patch, Third Party Advisory | |
| security@apache.org | https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwv | Issue Tracking, Mailing List, Vendor Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566f | Exploit, Issue Tracking, Patch, Third Party Advisory | |
| af854a3a-2127-422b-91ae-364da2661108 | https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwv | Issue Tracking, Mailing List, Vendor Advisory |
{
"affected": [
{
"affectedData": [
{
"product": "Apache Pulsar",
"vendor": "Apache Software Foundation",
"versions": [
{
"lessThanOrEqual": "2.7.4",
"status": "affected",
"version": "2.7",
"versionType": "custom"
},
{
"lessThanOrEqual": "2.8.3",
"status": "affected",
"version": "2.8",
"versionType": "custom"
},
{
"lessThanOrEqual": "2.9.2",
"status": "affected",
"version": "2.9",
"versionType": "custom"
},
{
"lessThanOrEqual": "2.10.1",
"status": "affected",
"version": "2.10",
"versionType": "custom"
},
{
"lessThanOrEqual": "2.6.4",
"status": "affected",
"version": "2.6 and earlier",
"versionType": "custom"
},
{
"lessThan": "3.0*",
"status": "unaffected",
"version": "3.0.0",
"versionType": "custom"
}
]
}
],
"source": "security@apache.org"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*",
"matchCriteriaId": "1DC4ED3C-514F-4895-B0D8-1160207FA2AD",
"versionEndIncluding": "2.6.4",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E1D90423-FEF6-41F0-82D3-2FD7AF67006B",
"versionEndExcluding": "2.7.5",
"versionStartIncluding": "2.7.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*",
"matchCriteriaId": "02284ABD-BFD3-4E2A-850A-CC12A7996E97",
"versionEndExcluding": "2.8.4",
"versionStartIncluding": "2.8.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*",
"matchCriteriaId": "C1A2D87A-55FC-42C0-BB48-E2B5B07EE1CE",
"versionEndExcluding": "2.9.3",
"versionStartIncluding": "2.9.0",
"vulnerable": true
},
{
"criteria": "cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*",
"matchCriteriaId": "F2E6D308-6DCF-483F-966B-2E618CEC10BF",
"versionEndExcluding": "2.10.2",
"versionStartIncluding": "2.10.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "The Apache Pulsar C++ Client does not verify peer TLS certificates when making HTTPS calls for the OAuth2.0 Client Credential Flow, even when tlsAllowInsecureConnection is disabled via configuration. This vulnerability allows an attacker to perform a man in the middle attack and intercept and/or modify the GET request that is sent to the ClientCredentialFlow \u0027issuer url\u0027. The intercepted credentials can be used to acquire authentication data from the OAuth2.0 server to then authenticate with an Apache Pulsar cluster. An attacker can only take advantage of this vulnerability by taking control of a machine \u0027between\u0027 the client and the server. The attacker must then actively manipulate traffic to perform the attack. The Apache Pulsar Python Client wraps the C++ client, so it is also vulnerable in the same way. This issue affects Apache Pulsar C++ Client and Python Client versions 2.7.0 to 2.7.4; 2.8.0 to 2.8.3; 2.9.0 to 2.9.2; 2.10.0 to 2.10.1; 2.6.4 and earlier. Any users running affected versions of the C++ Client or the Python Client should rotate vulnerable OAuth2.0 credentials, including client_id and client_secret. 2.7 C++ and Python Client users should upgrade to 2.7.5 and rotate vulnerable OAuth2.0 credentials. 2.8 C++ and Python Client users should upgrade to 2.8.4 and rotate vulnerable OAuth2.0 credentials. 2.9 C++ and Python Client users should upgrade to 2.9.3 and rotate vulnerable OAuth2.0 credentials. 2.10 C++ and Python Client users should upgrade to 2.10.2 and rotate vulnerable OAuth2.0 credentials. 3.0 C++ users are unaffected and 3.0 Python Client users will be unaffected when it is released. Any users running the C++ and Python Client for 2.6 or less should upgrade to one of the above patched versions."
},
{
"lang": "es",
"value": "El cliente Apache Pulsar C++ no verifica los certificados TLS de los peers al realizar llamadas HTTPS para el flujo de credenciales del cliente OAuth2.0, incluso cuando tlsAllowInsecureConnection est\u00e1 deshabilitado mediante la configuraci\u00f3n. Esta vulnerabilidad permite a un atacante realizar un ataque intermediario e interceptar y/o modificar la solicitud GET que se env\u00eda a la \u0027URL del emisor\u0027 de ClientCredentialFlow. Las credenciales interceptadas se pueden utilizar para adquirir datos de autenticaci\u00f3n del servidor OAuth2.0 para luego autenticarse con un cl\u00faster Apache Pulsar. Un atacante s\u00f3lo puede aprovechar esta vulnerabilidad tomando el control de una m\u00e1quina \"entre\" el cliente y el servidor. Luego, el atacante debe manipular activamente el tr\u00e1fico para realizar el ataque. El cliente Apache Pulsar Python envuelve el cliente C++, por lo que tambi\u00e9n es vulnerable de la misma manera. Este problema afecta a las versiones 2.7.0 a 2.7.4 del cliente Apache Pulsar C++ y del cliente Python; 2.8.0 a 2.8.3; 2.9.0 a 2.9.2; 2.10.0 a 2.10.1; 2.6.4 y anteriores. Cualquier usuario que ejecute versiones afectadas del Cliente C++ o del Cliente Python debe rotar las credenciales OAuth2.0 vulnerables, incluidas client_id y client_secret. Los usuarios de 2.7 C++ y Python Client deben actualizar a 2.7.5 y rotar las credenciales vulnerables de OAuth2.0. Los usuarios de 2.8 C++ y Python Client deben actualizar a 2.8.4 y rotar las credenciales vulnerables de OAuth2.0. Los usuarios de 2.9 C++ y Python Client deben actualizar a 2.9.3 y rotar las credenciales vulnerables de OAuth2.0. Los usuarios de 2.10 C++ y Python Client deben actualizar a 2.10.2 y rotar las credenciales vulnerables de OAuth2.0. Los usuarios de 3.0 C++ no se ven afectados y los usuarios de 3.0 Python Client no se ver\u00e1n afectados cuando se lance. Cualquier usuario que ejecute C++ y Python Client para 2.6 o menos debe actualizar a una de las versiones parcheadas anteriores."
}
],
"id": "CVE-2022-33684",
"lastModified": "2026-06-17T04:49:15.093",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
},
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 8.1,
"baseSeverity": "HIGH",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 5.9,
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2022-33684",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "total"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-05-02T18:56:43.494236Z",
"version": "2.0.3"
}
}
]
},
"published": "2022-11-04T12:15:13.123",
"references": [
{
"source": "security@apache.org",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566f"
},
{
"source": "security@apache.org",
"tags": [
"Issue Tracking",
"Mailing List",
"Vendor Advisory"
],
"url": "https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwv"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Exploit",
"Issue Tracking",
"Patch",
"Third Party Advisory"
],
"url": "https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566f"
},
{
"source": "af854a3a-2127-422b-91ae-364da2661108",
"tags": [
"Issue Tracking",
"Mailing List",
"Vendor Advisory"
],
"url": "https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwv"
}
],
"sourceIdentifier": "security@apache.org",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-295"
}
],
"source": "security@apache.org",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-295"
}
],
"source": "nvd@nist.gov",
"type": "Secondary"
},
{
"description": [
{
"lang": "en",
"value": "CWE-295"
}
],
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.