{"vulnerability": "CVE-2023-3042", "sightings": [{"uuid": "95be8e3e-3e2c-4d91-ac88-496cbb5e9c47", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-30421", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3ln7gixokjv2g", "content": "", "creation_timestamp": "2025-04-20T00:48:58.810467Z"}, {"uuid": "7197dc78-7486-4ab8-b0d7-de657b51e1e7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-3042", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18189", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-3042\n\ud83d\udd25 CVSS Score: 5.3 (cvssV3_1, Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)\n\ud83d\udd39 Description: In dotCMS, versions mentioned, a flaw in the NormalizationFilter does not strip double slashes (//) from URLs, potentially enabling bypasses for XSS and access controls. An example affected URL is  https://demo.dotcms.com//html/portlet/ext/files/edit_text_inc.jsp , which should return a 404 response but didn't. \n\nThe oversight in the default invalid URL character list can be viewed at the provided  GitHub link https://github.com/dotCMS/core/blob/master/dotCMS/src/main/java/com/dotcms/filters/NormalizationFilter.java#L37 .\u00a0\n\nTo mitigate, users can block URLs with double slashes at firewalls or utilize dotCMS config variables.\n\nSpecifically, they can use the DOT_URI_NORMALIZATION_FORBIDDEN_STRINGS environmental variable to add // to the list of invalid strings. \n\nAdditionally, the DOT_URI_NORMALIZATION_FORBIDDEN_REGEX variable offers more detailed control, for instance, to block //html.* URLs.\n\nFix Version:23.06+, LTS 22.03.7+, LTS 23.01.4+\n\ud83d\udccf Published: 2023-10-17T22:52:05.453Z\n\ud83d\udccf Modified: 2025-06-12T15:05:44.260Z\n\ud83d\udd17 References:\n1. https://www.dotcms.com/security/SI-68", "creation_timestamp": "2025-06-12T15:34:11.000000Z"}, {"uuid": "bc284792-e979-4e34-bc41-71605ec229c3", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-30421", "type": "seen", "source": "https://t.me/cvedetector/23397", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-30421 - Mjson strtod Denial of Service (DoS)\", \n  \"Content\": \"CVE ID : CVE-2023-30421 \nPublished : April 19, 2025, 10:15 p.m. | 48\u00a0minutes ago \nDescription : mystrtod in mjson 1.2.7 requires more than a billion iterations during processing of certain digit strings such as 8891110122900e913013935755114. \nSeverity: 2.9 | LOW \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"20 Apr 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-04-20T01:10:35.000000Z"}, {"uuid": "fc4aa1fd-1936-4465-bb02-290277834bdf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-30421", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/12599", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-30421\n\ud83d\udd25 CVSS Score: 2.9 (cvssV3_1, Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L)\n\ud83d\udd39 Description: mystrtod in mjson 1.2.7 requires more than a billion iterations during processing of certain digit strings such as 8891110122900e913013935755114.\n\ud83d\udccf Published: 2025-04-19T00:00:00.000Z\n\ud83d\udccf Modified: 2025-04-19T21:42:33.498Z\n\ud83d\udd17 References:\n1. https://github.com/boofish/json_bugs/blob/main/mjson\n2. https://github.com/cesanta/mjson/releases", "creation_timestamp": "2025-04-19T22:00:00.000000Z"}, {"uuid": "8665ac4d-0810-48fb-9077-1f3bf22c5856", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-30428", "type": "seen", "source": "https://t.me/cibsecurity/66534", "content": "\u203c CVE-2023-30428 \u203c\n\nIncorrect Authorization vulnerability in Apache Software Foundation Apache Pulsar Broker's Rest Producer allows authenticated user with a custom HTTP header to produce a message to any topic using the broker's admin role.This issue affects Apache Pulsar Brokers: from 2.9.0 through 2.9.5, from 2.10.0 before 2.10.4, 2.11.0.The vulnerability is exploitable when an attacker can connect directly to the Pulsar Broker. If an attacker is connecting through the Pulsar Proxy, there is no known way to exploit this authorization vulnerability.There are two known risks for affected users. First, an attacker could produce garbage messages to any topic in the cluster. Second, an attacker could produce messages to the topic level policies topic for other tenants and influence topic settings that could lead to exfiltration and/or deletion of messages for other tenants.2.8 Pulsar Broker users and earlier are unaffected.2.9 Pulsar Broker users should upgrade to one of the patched versions.2.10 Pulsar Broker users should upgrade to at least 2.10.4.2.11 Pulsar Broker users should upgrade to at least 2.11.1.3.0 Pulsar Broker users are unaffected.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-07-12T14:45:43.000000Z"}, {"uuid": "4a85529a-b120-45ef-b11f-5188d92396ce", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-30429", "type": "seen", "source": "https://t.me/cibsecurity/66524", "content": "\u203c CVE-2023-30429 \u203c\n\nIncorrect Authorization vulnerability in Apache Software Foundation Apache Pulsar.This issue affects Apache Pulsar: before 2.10.4, and 2.11.0.When a client connects to the Pulsar Function Worker via the Pulsar Proxy where the Pulsar Proxy uses mTLS authentication to authenticate with the Pulsar Function Worker, the Pulsar Function Worker incorrectly performs authorization by using the Proxy's role for authorization instead of the client's role, which can lead to privilege escalation, especially if the proxy is configured with a superuser role.The recommended mitigation for impacted users is to upgrade the Pulsar Function Worker to a patched version.2.10 Pulsar Function Worker users should upgrade to at least 2.10.4.2.11 Pulsar Function Worker users should upgrade to at least 2.11.1.3.0 Pulsar Function Worker users are unaffected.Any users running the Pulsar Function Worker for 2.9.* and earlier should upgrade to one of the above patched versions.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-07-12T14:45:27.000000Z"}]}