#cve20234966 — Public Fediverse posts

@simontsui Good question. It's not that simple :)

I agree with all of your observations. Personally, I like #CVE_2023_4966 the best for readability.

The cvecrowd crawler searches for #CVE20234966, #CVE2023_4966, #CVE_20234966, #CVE_2023_4966 just to not miss anything. However, the thing that makes it complicated is searching for the hashtags used. There are too many CVE numbers to search for all of them regularly.

When searching for #CVE results do not include ANY of the above formats. Ironically, what it does find is #CVE-2023-4966.

In addition to hashtags, I also use full text search. When searching for "CVE" it finds CVE-2023-4966, but not when its written as a hashtag.

So a reliable way to get my crawler to find CVE posts is to use either the word "CVE", perhaps in combination with a CVE ID as described above, or the hashtag #CVE.

@simontsui Good question. It's not that simple :)

I agree with all of your observations. Personally, I like #CVE_2023_4966 the best for readability.

The cvecrowd crawler searches for #CVE20234966, #CVE2023_4966, #CVE_20234966, #CVE_2023_4966 just to not miss anything. However, the thing that makes it complicated is searching for the hashtags used. There are too many CVE numbers to search for all of them regularly.

When searching for #CVE results do not include ANY of the above formats. Ironically, what it does find is #CVE-2023-4966.

In addition to hashtags, I also use full text search. When searching for "CVE" it finds CVE-2023-4966, but not when its written as a hashtag.

So a reliable way to get my crawler to find CVE posts is to use either the word "CVE", perhaps in combination with a CVE ID as described above, or the hashtag #CVE.

@simontsui Good question. It's not that simple :)

I agree with all of your observations. Personally, I like #CVE_2023_4966 the best for readability.

The cvecrowd crawler searches for #CVE20234966, #CVE2023_4966, #CVE_20234966, #CVE_2023_4966 just to not miss anything. However, the thing that makes it complicated is searching for the hashtags used. There are too many CVE numbers to search for all of them regularly.

When searching for #CVE results do not include ANY of the above formats. Ironically, what it does find is #CVE-2023-4966.

In addition to hashtags, I also use full text search. When searching for "CVE" it finds CVE-2023-4966, but not when its written as a hashtag.

So a reliable way to get my crawler to find CVE posts is to use either the word "CVE", perhaps in combination with a CVE ID as described above, or the hashtag #CVE.

@simontsui Good question. It's not that simple :)

I agree with all of your observations. Personally, I like #CVE_2023_4966 the best for readability.

The cvecrowd crawler searches for #CVE20234966, #CVE2023_4966, #CVE_20234966, #CVE_2023_4966 just to not miss anything. However, the thing that makes it complicated is searching for the hashtags used. There are too many CVE numbers to search for all of them regularly.

When searching for #CVE results do not include ANY of the above formats. Ironically, what it does find is #CVE-2023-4966.

In addition to hashtags, I also use full text search. When searching for "CVE" it finds CVE-2023-4966, but not when its written as a hashtag.

So a reliable way to get my crawler to find CVE posts is to use either the word "CVE", perhaps in combination with a CVE ID as described above, or the hashtag #CVE.

@simontsui Good question. It's not that simple :)

I agree with all of your observations. Personally, I like #CVE_2023_4966 the best for readability.

The cvecrowd crawler searches for #CVE20234966, #CVE2023_4966, #CVE_20234966, #CVE_2023_4966 just to not miss anything. However, the thing that makes it complicated is searching for the hashtags used. There are too many CVE numbers to search for all of them regularly.

When searching for #CVE results do not include ANY of the above formats. Ironically, what it does find is #CVE-2023-4966.

In addition to hashtags, I also use full text search. When searching for "CVE" it finds CVE-2023-4966, but not when its written as a hashtag.

So a reliable way to get my crawler to find CVE posts is to use either the word "CVE", perhaps in combination with a CVE ID as described above, or the hashtag #CVE.

POC for CVE-2023-4966 - Info disclosure in NetScaler ADC (formerly Citrix ADC) and NetScaler Gateway (formerly Citrix Gateway).

https://github.com/assetnote/exploits/tree/main/citrix/CVE-2023-4966

Related blog post: https://www.assetnote.io/resources/research/citrix-bleed-leaking-session-tokens-with-cve-2023-4966

#pentesting #redteam #hacking #CVE_2023_4966 #CVE_2023_4966 #CVE20234966

POC for CVE-2023-4966 - Info disclosure in NetScaler ADC (formerly Citrix ADC) and NetScaler Gateway (formerly Citrix Gateway).

https://github.com/assetnote/exploits/tree/main/citrix/CVE-2023-4966

Related blog post: https://www.assetnote.io/resources/research/citrix-bleed-leaking-session-tokens-with-cve-2023-4966

#pentesting #redteam #hacking #CVE_2023_4966 #CVE_2023_4966 #CVE20234966

POC for CVE-2023-4966 - Info disclosure in NetScaler ADC (formerly Citrix ADC) and NetScaler Gateway (formerly Citrix Gateway).

https://github.com/assetnote/exploits/tree/main/citrix/CVE-2023-4966

Related blog post: https://www.assetnote.io/resources/research/citrix-bleed-leaking-session-tokens-with-cve-2023-4966

#pentesting #redteam #hacking #CVE_2023_4966 #CVE_2023_4966 #CVE20234966

POC for CVE-2023-4966 - Info disclosure in NetScaler ADC (formerly Citrix ADC) and NetScaler Gateway (formerly Citrix Gateway).

https://github.com/assetnote/exploits/tree/main/citrix/CVE-2023-4966

Related blog post: https://www.assetnote.io/resources/research/citrix-bleed-leaking-session-tokens-with-cve-2023-4966

#pentesting #redteam #hacking #CVE_2023_4966 #CVE_2023_4966 #CVE20234966

POC for CVE-2023-4966 - Info disclosure in NetScaler ADC (formerly Citrix ADC) and NetScaler Gateway (formerly Citrix Gateway).

https://github.com/assetnote/exploits/tree/main/citrix/CVE-2023-4966

Related blog post: https://www.assetnote.io/resources/research/citrix-bleed-leaking-session-tokens-with-cve-2023-4966

#pentesting #redteam #hacking #CVE_2023_4966 #CVE_2023_4966 #CVE20234966

"🚨 Critical Flaws in Citrix NetScaler Expose Data & Enable DoS Attacks 🚨"

Citrix NetScaler has been hit with two critical vulnerabilities, CVE-2023-4966 and CVE-2023-4967, exposing sensitive data and enabling DoS attacks. The former, with a CVSS score of 9.4, allows remote exploitation without high-level access, while the latter, scoring 8.2, enables a Denial of Service attack on vulnerable devices. Citrix has rolled out security upgrades, urging customers to update to safeguard their systems. 🛡️🌐

CVE-2023-4966: This one's pretty severe and could allow unauthorized access to sensitive data without needing high-level access or user involvement.
CVE-2023-4967: Another biggie, this could enable a ‘Denial of Service attack’, basically shutting down our systems.

Source: GBHackers by Divya

Tags: #Citrix #NetScaler #Vulnerability #CyberSecurity #DataExposure #DoSAttack #CVE20234966 #CVE20234967 #CyberAttack #InfoSec

🔗 MITRE CVE-2023-4966
🔗 MITRE CVE-2023-4967