{"vulnerability": "CVE-2023-2453", "sightings": [{"uuid": "35cea2b4-0b82-4ec2-9585-cf587fa07cc8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24538", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/5240", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01\n\n\u66f4\u65b0\u4e86\uff1aCVE-2023\n\u63cf\u8ff0\uff1ago CVE-2023-24538 patch issue resolver - Kirkstone\nURL\uff1ahttps://github.com/skulkarni-mv/goIssue_kirkstone\n\n\u6807\u7b7e\uff1a#CVE-2023", "creation_timestamp": "2023-09-28T17:10:09.000000Z"}, {"uuid": "78a16542-810b-4f3b-b3b2-562eb4964da6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24538", "type": "published-proof-of-concept", "source": "https://t.me/GithubRedTeam/5269", "content": "GitHub\u76d1\u63a7\u6d88\u606f\u63d0\u9192\uff01\uff01\uff01 \n\n\u66f4\u65b0\u4e86\uff1aCVE-2023\n\u63cf\u8ff0\uff1ago CVE-2023-24538 patch issue resolver - Dunfell\nURL\uff1ahttps://github.com/skulkarni-mv/goIssue_dunfell\n\n\u6807\u7b7e\uff1a#CVE-2023", "creation_timestamp": "2023-10-04T05:31:37.000000Z"}, {"uuid": "b792b3f6-f794-43c6-bbff-dabed516bd7e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-2453", "type": "seen", "source": "https://t.me/cibsecurity/69854", "content": "\u203c CVE-2023-2453 \u203c\n\nThere is insufficient sanitization of tainted file names that are directly concatenated with a path that is subsequently passed to a \u00e2\u20ac\u02dcrequire_once\u00e2\u20ac\u2122 statement. This allows arbitrary files with the \u00e2\u20ac\u02dc.php\u00e2\u20ac\u2122 extension for which the absolute path is known to be included and executed. There are no known means in PHPFusion through which an attacker can upload and target a \u00e2\u20ac\u02dc.php\u00e2\u20ac\u2122 file payload.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-09-05T18:17:04.000000Z"}, {"uuid": "5db1446a-c109-4908-8f35-ace3a334e04e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24536", "type": "seen", "source": "https://t.me/arpsyndicate/4759", "content": "#ExploitObserverAlert\n\nCVE-2023-24536\n\nDESCRIPTION: Exploit Observer has 19 entries in 4 file formats related to CVE-2023-24536. Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.\n\nFIRST-EPSS: 0.004530000\nNVD-IS: 3.6\nNVD-ES: 3.9\nARPS-PRIORITY: 0.7024624", "creation_timestamp": "2024-04-23T18:33:28.000000Z"}, {"uuid": "b6b8a174-1429-4fdb-9ee7-e371207d0070", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24534", "type": "seen", "source": "https://t.me/arpsyndicate/4754", "content": "#ExploitObserverAlert\n\nCVE-2023-24534\n\nDESCRIPTION: Exploit Observer has 21 entries in 4 file formats related to CVE-2023-24534. HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers.\n\nFIRST-EPSS: 0.001810000\nNVD-IS: 3.6\nNVD-ES: 3.9\nARPS-PRIORITY: 0.7008381", "creation_timestamp": "2024-04-23T18:07:43.000000Z"}, {"uuid": "b3b6716a-f2da-4727-ad13-f8db8c26b3bd", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-2453", "type": "seen", "source": "https://t.me/ctinow/134883", "content": "https://ift.tt/lkejMxo\nCyRC Vulnerability Advisory: CVE-2023-2453 Local File Inclusion in Forum Infusion and CVE-2023-4480 Arbitrary File Read in Fusion File Manager", "creation_timestamp": "2023-09-05T21:06:26.000000Z"}, {"uuid": "b4ca9b81-7b97-4bfc-865d-7200d24c469b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24536", "type": "seen", "source": "Telegram/K3ep4gI8iJ6OKpuCAJKrmPD6WzBkMhgZ0G0vn2ROnvTVAtSI", "content": "", "creation_timestamp": "2025-02-14T10:05:08.000000Z"}, {"uuid": "80fd1d40-3742-45e2-b5f2-7a952236d356", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24534", "type": "seen", "source": "Telegram/Srh7buvg7eZ7zNdnnNwHbHqlj4u7C6nnLhCyRvA8lqlOes9P", "content": "", "creation_timestamp": "2025-02-14T10:05:08.000000Z"}, {"uuid": "66019f12-b113-49ad-b571-88a923d1baee", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24539", "type": "seen", "source": "https://t.me/cibsecurity/63900", "content": "\u203c CVE-2023-24539 \u203c\n\nAngle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-05-11T20:15:27.000000Z"}, {"uuid": "3e9384f4-f5ed-4d4f-b570-92de3ade97f5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24533", "type": "seen", "source": "https://t.me/cibsecurity/59693", "content": "\u203c CVE-2023-24533 \u203c\n\nMultiplication of certain unreduced P-256 scalars produce incorrect results. There are no protocols known at this time that can be attacked due to this.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-03-08T22:24:06.000000Z"}, {"uuid": "4613098e-b355-4633-a101-3a7d6a88f3fe", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24538", "type": "seen", "source": "https://t.me/cibsecurity/61576", "content": "\u203c CVE-2023-24538 \u203c\n\nTemplates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. \"var a = {{.}}\"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-04-06T20:27:18.000000Z"}, {"uuid": "73bb4048-85b1-436e-ad9c-5aeed70fd86a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24532", "type": "seen", "source": "https://t.me/cibsecurity/59685", "content": "\u203c CVE-2023-24532 \u203c\n\nThe ScalarMult and ScalarBaseMult methods of the P256 Curve may return an incorrect result if called with some specific unreduced scalars (a scalar larger than the order of the curve). This does not impact usages of crypto/ecdsa or crypto/ecdh.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-03-08T22:23:56.000000Z"}, {"uuid": "27e4c67d-1114-4bd6-b9d6-6aa1dbc397e1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24536", "type": "seen", "source": "https://t.me/cibsecurity/61572", "content": "\u203c CVE-2023-24536 \u203c\n\nMultipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-04-06T20:27:11.000000Z"}, {"uuid": "e910a939-ac21-48a1-9bf9-a6282d045547", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2023-24531", "type": "seen", "source": "https://bsky.app/profile/andresbohren.bsky.social/post/3mmubm7gb3s22", "content": "\ud83d\udea8New #JabraDirect Version has been published\n- Addresses several vulnerabilities:\nCVE-2025-22871, CVE-2024-24790, CVE-2023-24531, CVE-2023-29827\ntinyurl.com/5f7mmkvf", "creation_timestamp": "2026-05-27T19:48:15.840294Z"}]}