{"vulnerability": "CVE-2023-5292", "sightings": [{"uuid": "9b79552a-2ce6-4ad3-a8fc-1b637eb98116", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/lobsters-feed.bsky.social/post/3lrgl2zshmy2x", "content": "", "creation_timestamp": "2025-06-12T18:40:05.102461Z"}, {"uuid": "7d8c5a8d-476b-46be-9cb7-a0ebddb4b8ca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52927", "type": "seen", "source": "https://www.cisa.gov/news-events/ics-advisories/icsa-25-162-05", "content": "", "creation_timestamp": "2025-06-12T10:00:00.000000Z"}, {"uuid": "844eff7c-eae9-411b-8a25-450ab67fe106", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3lr6glg3qis27", "content": "", "creation_timestamp": "2025-06-09T12:58:29.817717Z"}, {"uuid": "279ed7df-9294-45f7-9813-a516afd19ac8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3lr6glg3tgk27", "content": "", "creation_timestamp": "2025-06-09T12:58:30.892456Z"}, {"uuid": "6aabcd52-c427-45c5-a144-542875b8b4bf", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3lr6glg3ufs27", "content": "", "creation_timestamp": "2025-06-09T12:58:31.925273Z"}, {"uuid": "df5064ff-e825-4903-9838-cc7a1263db83", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3lr6glg3uft27", "content": "", "creation_timestamp": "2025-06-09T12:58:32.998745Z"}, {"uuid": "cf70cda0-b0b0-4b84-861d-bec6ae0827e5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3lr6glg3ufu27", "content": "", "creation_timestamp": "2025-06-09T12:58:34.070760Z"}, {"uuid": "be403101-cf2d-43ed-b4bf-c58a3ee4e05e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3lr6glg3vf427", "content": "", "creation_timestamp": "2025-06-09T12:58:35.145747Z"}, {"uuid": "697a6c06-3d59-41d7-b265-be16d91a38f6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3lr7thm2jbg2b", "content": "", "creation_timestamp": "2025-06-10T02:21:38.310327Z"}, {"uuid": "ff4016aa-6821-442b-9250-d4fe6124f4a2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52927", "type": "seen", "source": "https://bsky.app/profile/linkersec.bsky.social/post/3lu6rdr3jfk27", "content": "", "creation_timestamp": "2025-07-17T20:26:44.122816Z"}, {"uuid": "eaad74ba-1be0-42e0-9638-8726319b4620", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m4nsvcgtz22w", "content": "", "creation_timestamp": "2025-11-02T15:25:53.859122Z"}, {"uuid": "8ea46589-9c05-4be1-a5ce-3de5e13b3ad4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5effot7r22d", "content": "", "creation_timestamp": "2025-11-11T14:55:45.303633Z"}, {"uuid": "2613e280-33f0-4764-b9f6-5463b5c80bd9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5effotfmk2d", "content": "", "creation_timestamp": "2025-11-11T14:55:48.475154Z"}, {"uuid": "8f124fae-aa2d-4ff4-9314-181b4fef1d5b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5effotenc2d", "content": "", "creation_timestamp": "2025-11-11T14:55:46.932945Z"}, {"uuid": "49bc8ca7-2f6a-4848-8ed0-cdc937370cad", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5effothl22d", "content": "", "creation_timestamp": "2025-11-11T14:55:50.022481Z"}, {"uuid": "0977e14b-9524-4b40-9d3e-32bddc160fde", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5effothl32d", "content": "", "creation_timestamp": "2025-11-11T14:55:51.593779Z"}, {"uuid": "1cf56bb0-9ae5-4f1e-b443-429d1e03a0ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5effotikd2d", "content": "", "creation_timestamp": "2025-11-11T14:55:53.131801Z"}, {"uuid": "1cafaffb-45cb-491d-9c1f-164cc0b84acb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5efqcqxnk2q", "content": "", "creation_timestamp": "2025-11-11T15:01:41.301976Z"}, {"uuid": "1e28e180-0bd6-459f-98a3-babfd8631448", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5efqde3xc2q", "content": "", "creation_timestamp": "2025-11-11T15:01:41.824662Z"}, {"uuid": "b0c70cc2-6489-4fbb-bd53-92c76a23886c", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/qiancx.bsky.social/post/3lxpwicg23q2f", "content": "", "creation_timestamp": "2025-08-31T20:29:28.259358Z"}, {"uuid": "c45477bb-29b4-4373-b326-ef3ac2f089e4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/dasgeldco.bsky.social/post/3lxpwj56oqd2l", "content": "", "creation_timestamp": "2025-08-31T20:29:56.157360Z"}, {"uuid": "c69085f4-e55b-4547-a043-242747b1295e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2023-52920", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "f87b60f2-a164-4f38-832a-04676e01656d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2023-52926", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "942305ec-c382-4184-860e-7ae41e24a358", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "4f29edb9-4c4b-44ca-b041-9b050656b6ae", "vulnerability": "CVE-2023-52921", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0316/", "content": "", "creation_timestamp": "2026-03-19T00:00:00.000000Z"}, {"uuid": "24455202-552e-4b48-ad43-f67816ddbc91", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52926", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "38ab7c18-5d7c-4d74-8d5c-d3fec2155a3d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52925", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "6c69628b-8f66-403b-a602-c68ac632904e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52925", "type": "seen", "source": "https://t.me/cvedetector/17287", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52925 - Apache Linux Kernel Nf_tables Expired Entry Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-52925 \nPublished : Feb. 5, 2025, 10:15 a.m. | 1\u00a0hour, 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: nf_tables: don't fail inserts if duplicate has expired  \n  \nnftables selftests fail:  \nrun-tests.sh testcases/sets/0044interval_overlap_0  \nExpected: 0-2 . 0-3, got:  \nW: [FAILED]     ./testcases/sets/0044interval_overlap_0: got 1  \n  \nInsertion must ignore duplicate but expired entries.  \n  \nMoreover, there is a strange asymmetry in nft_pipapo_activate:  \n  \nIt refetches the current element, whereas the other ->activate callbacks  \n(bitmap, hash, rhash, rbtree) use elem->priv.  \nSame for .remove: other set implementations take elem->priv,  \nnft_pipapo_remove fetches elem->priv, then does a relookup,  \nremove this.  \n  \nI suspect this was the reason for the change that prompted the  \nremoval of the expired check in pipapo_get() in the first place,  \nbut skipping exired elements there makes no sense to me, this helper  \nis used for normal get requests, insertions (duplicate check)  \nand deactivate callback.  \n  \nIn first two cases expired elements must be skipped.  \n  \nFor ->deactivate(), this gets called for DELSETELEM, so it  \nseems to me that expired elements should be skipped as well, i.e.  \ndelete request should fail with -ENOENT error. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-05T13:18:00.000000Z"}, {"uuid": "812f9ac9-b974-4781-847b-4ff6219af820", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52924", "type": "seen", "source": "https://t.me/cvedetector/17286", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52924 - Apache Netfilter nf_tables Use Count Leak Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2023-52924 \nPublished : Feb. 5, 2025, 10:15 a.m. | 1\u00a0hour, 36\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: nf_tables: don't skip expired elements during walk  \n  \nThere is an asymmetry between commit/abort and preparation phase if the  \nfollowing conditions are met:  \n  \n1. set is a verdict map (\"1.2.3.4 : jump foo\")  \n2. timeouts are enabled  \n  \nIn this case, following sequence is problematic:  \n  \n1. element E in set S refers to chain C  \n2. userspace requests removal of set S  \n3. kernel does a set walk to decrement chain->use count for all elements  \n   from preparation phase  \n4. kernel does another set walk to remove elements from the commit phase  \n   (or another walk to do a chain->use increment for all elements from  \n    abort phase)  \n  \nIf E has already expired in 1), it will be ignored during list walk, so its use count  \nwon't have been changed.  \n  \nThen, when set is culled, ->destroy callback will zap the element via  \nnf_tables_set_elem_destroy(), but this function is only safe for  \nelements that have been deactivated earlier from the preparation phase:  \nlack of earlier deactivate removes the element but leaks the chain use  \ncount, which results in a WARN splat when the chain gets removed later,  \nplus a leak of the nft_chain structure.  \n  \nUpdate pipapo_get() not to skip expired elements, otherwise flush  \ncommand reports bogus ENOENT errors. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-05T13:17:56.000000Z"}, {"uuid": "ee9efa81-76a7-4759-a21f-1de9ce605326", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52927", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/7554", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-52927\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: allow exp not to be removed in nf_ct_find_expectation\n\nCurrently nf_conntrack_in() calling nf_ct_find_expectation() will\nremove the exp from the hash table. However, in some scenario, we\nexpect the exp not to be removed when the created ct will not be\nconfirmed, like in OVS and TC conntrack in the following patches.\n\nThis patch allows exp not to be removed by setting IPS_CONFIRMED\nin the status of the tmpl.\n\ud83d\udccf Published: 2025-03-14T14:25:59.166Z\n\ud83d\udccf Modified: 2025-03-14T14:25:59.166Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/3fa58a6fbd1e9e5682d09cdafb08fba004cb12ec\n2. https://git.kernel.org/stable/c/4914109a8e1e494c6aa9852f9e84ec77a5fc643f", "creation_timestamp": "2025-03-14T14:45:09.000000Z"}, {"uuid": "d94086b5-1480-4d72-a724-18d9d4b17748", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52920", "type": "seen", "source": "https://t.me/cvedetector/9855", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52920 - Linux Kernel BPF verifier jump history manipulation vulnerability.\", \n  \"Content\": \"CVE ID : CVE-2023-52920 \nPublished : Nov. 5, 2024, 10:15 a.m. | 38\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nbpf: support non-r10 register spill/fill to/from stack in precision tracking  \n  \nUse instruction (jump) history to record instructions that performed  \nregister spill/fill to/from stack, regardless if this was done through  \nread-only r10 register, or any other register after copying r10 into it  \n*and* potentially adjusting offset.  \n  \nTo make this work reliably, we push extra per-instruction flags into  \ninstruction history, encoding stack slot index (spi) and stack frame  \nnumber in extra 10 bit flags we take away from prev_idx in instruction  \nhistory. We don't touch idx field for maximum performance, as it's  \nchecked most frequently during backtracking.  \n  \nThis change removes basically the last remaining practical limitation of  \nprecision backtracking logic in BPF verifier. It fixes known  \ndeficiencies, but also opens up new opportunities to reduce number of  \nverified states, explored in the subsequent patches.  \n  \nThere are only three differences in selftests' BPF object files  \naccording to veristat, all in the positive direction (less states).  \n  \nFile                                    Program        Insns (A)  Insns (B)  Insns  (DIFF)  States (A)  States (B)  States (DIFF)  \n--------------------------------------  -------------  ---------  ---------  -------------  ----------  ----------  -------------  \ntest_cls_redirect_dynptr.bpf.linked3.o  cls_redirect        2987       2864  -123 (-4.12%)         240         231    -9 (-3.75%)  \nxdp_synproxy_kern.bpf.linked3.o         syncookie_tc       82848      82661  -187 (-0.23%)        5107        5073   -34 (-0.67%)  \nxdp_synproxy_kern.bpf.linked3.o         syncookie_xdp      85116      84964  -152 (-0.18%)        5162        5130   -32 (-0.62%)  \n  \nNote, I avoided renaming jmp_history to more generic insn_hist to  \nminimize number of lines changed and potential merge conflicts between  \nbpf and bpf-next trees.  \n  \nNotice also cur_hist_entry pointer reset to NULL at the beginning of  \ninstruction verification loop. This pointer avoids the problem of  \nrelying on last jump history entry's insn_idx to determine whether we  \nalready have entry for current instruction or not. It can happen that we  \nadded jump history entry because current instruction is_jmp_point(), but  \nalso we need to add instruction flags for stack access. In this case, we  \ndon't want to entries, so we need to reuse last added entry, if it is  \npresent.  \n  \nRelying on insn_idx comparison has the same ambiguity problem as the one  \nthat was fixed recently in [0], so we avoid that.  \n  \n  [0]  \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"05 Nov 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-11-05T12:11:39.000000Z"}, {"uuid": "be61f152-6dc1-4619-837c-6449c3c1622f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52925", "type": "seen", "source": "Telegram/_S907cuPrzPbyPOKhXebocU8CM3GFwnNNMWrLt5wPiBBcJsK", "content": "", "creation_timestamp": "2025-02-06T02:43:28.000000Z"}, {"uuid": "dd232791-1192-4694-96d7-4fed5030c44a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-5292", "type": "seen", "source": "https://t.me/cibsecurity/72668", "content": "\u203c CVE-2023-5292 \u203c\n\nThe Advanced Custom Fields: Extended plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'acfe_form' shortcode in versions up to, and including, 0.8.9.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers with contributor-level and above permissions to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.\n\n\ud83d\udcd6 Read\n\nvia \"National Vulnerability Database\".", "creation_timestamp": "2023-10-20T12:41:08.000000Z"}, {"uuid": "5ba25722-6f98-48fa-b725-ccd14c5a6e60", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52921", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113507065706456332", "content": "", "creation_timestamp": "2024-11-19T01:39:33.223650Z"}, {"uuid": "086ef379-b709-47d8-956a-032d0ca89ed5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52924", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhgrs6p23m2k", "content": "", "creation_timestamp": "2025-02-05T14:28:28.096497Z"}, {"uuid": "e4abe862-12f5-4a82-9f55-cd92e5b8324e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52925", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhgrs6sikw27", "content": "", "creation_timestamp": "2025-02-05T14:28:28.584836Z"}, {"uuid": "6c39c57a-9ccf-48aa-b8ae-258840090a70", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/allelesecurity.bsky.social/post/3lgvig44ibk2a", "content": "", "creation_timestamp": "2025-01-29T17:25:24.963874Z"}, {"uuid": "21842b3f-b0de-4bd7-9aea-5c1dfdfc7390", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/allelesecurity.bsky.social/post/3lgvig44vx22a", "content": "", "creation_timestamp": "2025-01-29T17:25:27.540463Z"}, {"uuid": "8d646a05-0a51-4eba-82a5-1ab0b6814a67", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/allelesecurity.bsky.social/post/3lgvig44s222a", "content": "", "creation_timestamp": "2025-01-29T17:25:25.469206Z"}, {"uuid": "b77d92e7-29e5-44e6-8bd2-a6f90f378973", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/allelesecurity.bsky.social/post/3lgvig44szc2a", "content": "", "creation_timestamp": "2025-01-29T17:25:25.983850Z"}, {"uuid": "418d9e40-b3ef-400b-a3fe-c27f98fb4b0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/allelesecurity.bsky.social/post/3lgvig44uxs2a", "content": "", "creation_timestamp": "2025-01-29T17:25:27.034565Z"}, {"uuid": "2714b8ca-9bd9-483c-9ba2-4edac7c7bf0b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52926", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3liw6d4pu4f2t", "content": "", "creation_timestamp": "2025-02-24T10:47:48.370551Z"}, {"uuid": "92199894-4483-408c-ad22-220a8bfb90c2", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "cve-2023-52927", "type": "seen", "source": "https://bsky.app/profile/raptor.infosec.exchange.ap.brid.gy/post/3ltn4vk7xtlc2", "content": "", "creation_timestamp": "2025-07-10T20:05:51.332399Z"}, {"uuid": "595bdef8-57cb-4054-af39-866b9b9d1310", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://infosec.exchange/users/andersonc0d3/statuses/115480792819056345", "content": "", "creation_timestamp": "2025-11-02T15:24:18.750575Z"}, {"uuid": "e5a2bedf-0e06-4894-b453-b914488ce99d", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m4nsv3o6g22w", "content": "", "creation_timestamp": "2025-11-02T15:25:52.359765Z"}, {"uuid": "11054070-4284-4219-942b-e1a25cbaa1ea", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m4nsv3oebk2w", "content": "", "creation_timestamp": "2025-11-02T15:25:52.874657Z"}, {"uuid": "2eab97cb-17d4-41fc-8c86-b56d017e7e61", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m4nsv7arfs2w", "content": "", "creation_timestamp": "2025-11-02T15:25:53.368359Z"}, {"uuid": "d2446c14-97fc-4ef9-b2aa-df2de8c3ad60", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52920", "type": "seen", "source": "https://vulnerability.circl.lu/bundle/816dcc8e-f25a-4895-9b59-1bbd9caeccb8", "content": "", "creation_timestamp": "2025-12-03T14:14:49.267740Z"}, {"uuid": "cbda0d52-7100-4870-80f6-ffdf5e094846", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52923", "type": "seen", "source": "https://t.me/cvedetector/15884", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52923 - Linux Kernel Netfilter nf_tables Dead Element Unlinking Anywhere\", \n  \"Content\": \"CVE ID : CVE-2023-52923 \nPublished : Jan. 20, 2025, 11:15 a.m. | 37\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: nf_tables: adapt set backend to use GC transaction API  \n  \nUse the GC transaction API to replace the old and buggy gc API and the  \nbusy mark approach.  \n  \nNo set elements are removed from async garbage collection anymore,  \ninstead the _DEAD bit is set on so the set element is not visible from  \nlookup path anymore. Async GC enqueues transaction work that might be  \naborted and retried later.  \n  \nrbtree and pipapo set backends does not set on the _DEAD bit from the  \nsync GC path since this runs in control plane path where mutex is held.  \nIn this case, set elements are deactivated, removed and then released  \nvia RCU callback, sync GC never fails. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"20 Jan 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-01-20T13:22:16.000000Z"}, {"uuid": "f4ce458d-ccd6-4c02-92c3-fb56446a5c51", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113561221342263509", "content": "", "creation_timestamp": "2024-11-28T15:12:03.310305Z"}, {"uuid": "ff461983-eb84-4292-b249-37014f974cd4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52923", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113860303604167825", "content": "", "creation_timestamp": "2025-01-20T10:52:35.796341Z"}, {"uuid": "8ddd3e8d-491c-4b0a-b697-9647154a578e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52923", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lg67kv6hlc2n", "content": "", "creation_timestamp": "2025-01-20T11:15:45.833848Z"}, {"uuid": "4eb5b297-b188-4ddd-92d4-cc25ee9f6966", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52923", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lg6alqyutb2u", "content": "", "creation_timestamp": "2025-01-20T11:34:08.675229Z"}, {"uuid": "d7693e45-c824-45d2-b2ad-d009b182455a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52924", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhgdnyryet27", "content": "", "creation_timestamp": "2025-02-05T10:15:39.589648Z"}, {"uuid": "dd5e3880-d634-4fb6-8c51-7e210b2ee303", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52925", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhgdo36sjb2h", "content": "", "creation_timestamp": "2025-02-05T10:15:42.838564Z"}, {"uuid": "7079ca4c-0708-45bc-8cb1-f8afb8fe0686", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52927", "type": "seen", "source": "https://bsky.app/profile/pmloik.bsky.social/post/3ltns4gc56a2v", "content": "", "creation_timestamp": "2025-07-11T02:25:08.975900Z"}, {"uuid": "94438ffe-c6f0-4229-b5d2-5ec82b7b8e80", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/alleleintel.com/post/3m5efqde4wk2q", "content": "", "creation_timestamp": "2025-11-11T15:01:42.382424Z"}, {"uuid": "693ef780-7ea3-4725-a2c1-7e76c059f534", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52927", "type": "published-proof-of-concept", "source": "https://t.me/orderofsixangles/2659", "content": "CVE-2023-52927 - Turning a Forgotten Syzkaller Report into kCTF Exploit\n\nhttps://seadragnol.github.io/posts/CVE-2023-52927/", "creation_timestamp": "2025-07-08T04:20:09.000000Z"}, {"uuid": "6b636e6b-1745-42e4-aa9f-2cfd1445fb89", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52923", "type": "seen", "source": "https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-0398/", "content": "", "creation_timestamp": "2026-04-02T17:00:00.000000Z"}, {"uuid": "9c07f140-775c-4074-bdea-1a5891fe9690", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52926", "type": "seen", "source": "https://t.me/cvedetector/18791", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52926 - Linux Kernel IORING Op Read Use-After-Free\", \n  \"Content\": \"CVE ID : CVE-2023-52926 \nPublished : Feb. 24, 2025, 9:15 a.m. | 1\u00a0hour, 33\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nIORING_OP_READ did not correctly consume the provided buffer list when  \nread i/o returned < 0 (except for -EAGAIN and -EIOCBQUEUED return).  \nThis can lead to a potential use-after-free when the completion via  \nio_rw_done runs at separate context. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"24 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-24T12:06:20.000000Z"}, {"uuid": "d87ce1c9-2327-400f-9b5a-9802288e5b6a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52923", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/2356", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-52923\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: adapt set backend to use GC transaction API\n\nUse the GC transaction API to replace the old and buggy gc API and the\nbusy mark approach.\n\nNo set elements are removed from async garbage collection anymore,\ninstead the _DEAD bit is set on so the set element is not visible from\nlookup path anymore. Async GC enqueues transaction work that might be\naborted and retried later.\n\nrbtree and pipapo set backends does not set on the _DEAD bit from the\nsync GC path since this runs in control plane path where mutex is held.\nIn this case, set elements are deactivated, removed and then released\nvia RCU callback, sync GC never fails.\n\ud83d\udccf Published: 2025-01-20T10:48:13.723Z\n\ud83d\udccf Modified: 2025-01-20T10:48:13.723Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/cb4d00b563675ba8ff6ef94b077f58d816f68ba3\n2. https://git.kernel.org/stable/c/c357648929c8dff891502349769aafb8f0452bc2\n3. https://git.kernel.org/stable/c/146c76866795553dbc19998f36718d7986ad302b\n4. https://git.kernel.org/stable/c/479a2cf5259347d6a1f658b0f791d27a34908e91\n5. https://git.kernel.org/stable/c/df650d6a4bf47248261b61ef6b174d7c54034d15\n6. https://git.kernel.org/stable/c/e4d71d6a9c7db93f7bf20c3a0f0659d63d7de681\n7. https://git.kernel.org/stable/c/f6c383b8c31a93752a52697f8430a71dcbc46adf", "creation_timestamp": "2025-01-20T10:59:53.000000Z"}, {"uuid": "947f9db0-9bc1-4041-a728-78bb8079c918", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/18340", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2023-52922\n\ud83d\udd25 CVSS Score: N/A\n\ud83d\udd39 Description: In the Linux kernel, the following vulnerability has been resolved:\n\ncan: bcm: Fix UAF in bcm_proc_show()\n\nBUG: KASAN: slab-use-after-free in bcm_proc_show+0x969/0xa80\nRead of size 8 at addr ffff888155846230 by task cat/7862\n\nCPU: 1 PID: 7862 Comm: cat Not tainted 6.5.0-rc1-00153-gc8746099c197 #230\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014\nCall Trace:\n \n dump_stack_lvl+0xd5/0x150\n print_report+0xc1/0x5e0\n kasan_report+0xba/0xf0\n bcm_proc_show+0x969/0xa80\n seq_read_iter+0x4f6/0x1260\n seq_read+0x165/0x210\n proc_reg_read+0x227/0x300\n vfs_read+0x1d5/0x8d0\n ksys_read+0x11e/0x240\n do_syscall_64+0x35/0xb0\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nAllocated by task 7846:\n kasan_save_stack+0x1e/0x40\n kasan_set_track+0x21/0x30\n __kasan_kmalloc+0x9e/0xa0\n bcm_sendmsg+0x264b/0x44e0\n sock_sendmsg+0xda/0x180\n ____sys_sendmsg+0x735/0x920\n ___sys_sendmsg+0x11d/0x1b0\n __sys_sendmsg+0xfa/0x1d0\n do_syscall_64+0x35/0xb0\n entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nFreed by task 7846:\n kasan_save_stack+0x1e/0x40\n kasan_set_track+0x21/0x30\n kasan_save_free_info+0x27/0x40\n ____kasan_slab_free+0x161/0x1c0\n slab_free_freelist_hook+0x119/0x220\n __kmem_cache_free+0xb4/0x2e0\n rcu_core+0x809/0x1bd0\n\nbcm_op is freed before procfs entry be removed in bcm_release(),\nthis lead to bcm_proc_show() may read the freed bcm_op.\n\ud83d\udccf Published: 2024-11-28T15:09:51.360Z\n\ud83d\udccf Modified: 2025-06-13T20:05:35.471Z\n\ud83d\udd17 References:\n1. https://git.kernel.org/stable/c/11b8e27ed448baa385d90154a141466bd5e92f18\n2. https://git.kernel.org/stable/c/9b58d36d0c1ea29a9571e0222a9c29df0ccfb7ff\n3. https://git.kernel.org/stable/c/9533dbfac0ff7edd77a5fa2c24974b1d66c8b0a6\n4. https://git.kernel.org/stable/c/cf254b4f68e480e73dab055014e002b77aed30ed\n5. https://git.kernel.org/stable/c/3c3941bb1eb53abe7d640ffee5c4d6b559829ab3\n6. https://git.kernel.org/stable/c/995f47d76647708ec26c6e388663ad4f3f264787\n7. https://git.kernel.org/stable/c/dfd0aa26e9a07f2ce546ccf8304ead6a2914e8a7\n8. https://git.kernel.org/stable/c/55c3b96074f3f9b0aee19bf93cd71af7516582bb", "creation_timestamp": "2025-06-13T20:35:34.000000Z"}, {"uuid": "ee516c89-1573-45a3-9593-f5f1ddd1740b", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52927", "type": "seen", "source": "https://t.me/cvedetector/20296", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2023-52927 - Open vSwitch Netfilter Conntrack Expectation Removal Vulnerability (Information Disclosure)\", \n  \"Content\": \"CVE ID : CVE-2023-52927 \nPublished : March 14, 2025, 3:15 p.m. | 15\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \nnetfilter: allow exp not to be removed in nf_ct_find_expectation  \n  \nCurrently nf_conntrack_in() calling nf_ct_find_expectation() will  \nremove the exp from the hash table. However, in some scenario, we  \nexpect the exp not to be removed when the created ct will not be  \nconfirmed, like in OVS and TC conntrack in the following patches.  \n  \nThis patch allows exp not to be removed by setting IPS_CONFIRMED  \nin the status of the tmpl. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"14 Mar 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-03-14T16:42:29.000000Z"}, {"uuid": "b8ffcc61-ebd6-4da2-899b-6cf7546cef32", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52924", "type": "seen", "source": "Telegram/wWfwHxa8r4csvCY5OWXBy4LKMLF6OyMrvichRZw8oaZMtfWO", "content": "", "creation_timestamp": "2025-02-06T02:43:28.000000Z"}, {"uuid": "76bd15c5-1b79-459c-96c8-8a57e22e0336", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52924", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113950532906464739", "content": "", "creation_timestamp": "2025-02-05T09:19:05.679390Z"}, {"uuid": "41f87150-6d43-4658-b998-6e8ba65279a8", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52925", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113950532922569529", "content": "", "creation_timestamp": "2025-02-05T09:19:06.047360Z"}, {"uuid": "c371faf2-6002-4ec0-8c49-4b828d892938", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52924", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113950551622532897", "content": "", "creation_timestamp": "2025-02-05T09:23:51.671751Z"}, {"uuid": "ecb0e583-83aa-43cd-8c4e-6d0bb066473f", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52925", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113950551638476340", "content": "", "creation_timestamp": "2025-02-05T09:23:51.764924Z"}, {"uuid": "502cf237-480b-4b4c-838a-f8822bd520fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/allelesecurity.bsky.social/post/3lgvig44tyk2a", "content": "", "creation_timestamp": "2025-01-29T17:25:26.537432Z"}, {"uuid": "50c80a81-aaba-4b9e-a0d7-21e148f4c7c6", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52922", "type": "seen", "source": "https://bsky.app/profile/allelesecurity.bsky.social/post/3lgvig54hpk2a", "content": "", "creation_timestamp": "2025-01-29T17:25:28.042512Z"}, {"uuid": "d36e759b-c11a-4e38-a858-d823ac2242b7", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2023-52927", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lke2qfqmwp2m", "content": "", "creation_timestamp": "2025-03-14T16:46:08.091141Z"}]}