home.social

#printnightmare β€” Public Fediverse posts

Live and recent posts from across the Fediverse tagged #printnightmare, aggregated by home.social.

  1. π‡πŽπ– π“πŽ πƒπˆπ’π€ππ‹π„ ππ‘πˆππ“ π’ππŽπŽπ‹π„π‘ 𝐎𝐍 πƒπŽπŒπ€πˆπ π‚πŽππ“π‘πŽπ‹π‹π„π‘π’

    Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί Watch my YouTube video bellow on how to disable Print Spooler on Domain Controllers πŸ‘‡ πŸ‘‡
    youtu.be/O80HHKdnbcQ

    #cswlrd #printspooler #domaincontrollers #printnightmare #videotutorial

  2. π‡πŽπ– π“πŽ πƒπˆπ’π€ππ‹π„ ππ‘πˆππ“ π’ππŽπŽπ‹π„π‘ 𝐎𝐍 πƒπŽπŒπ€πˆπ π‚πŽππ“π‘πŽπ‹π‹π„π‘π’

    Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί Watch my YouTube video bellow on how to disable Print Spooler on Domain Controllers πŸ‘‡ πŸ‘‡
    youtu.be/O80HHKdnbcQ

    #cswlrd #printspooler #domaincontrollers #printnightmare #videotutorial

  3. π‡πŽπ– π“πŽ πƒπˆπ’π€ππ‹π„ ππ‘πˆππ“ π’ππŽπŽπ‹π„π‘ 𝐎𝐍 πƒπŽπŒπ€πˆπ π‚πŽππ“π‘πŽπ‹π‹π„π‘π’

    Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί Watch my YouTube video bellow on how to disable Print Spooler on Domain Controllers πŸ‘‡ πŸ‘‡
    youtu.be/O80HHKdnbcQ

    #cswlrd #printspooler #domaincontrollers #printnightmare #videotutorial

  4. π‡πŽπ– π“πŽ πƒπˆπ’π€ππ‹π„ ππ‘πˆππ“ π’ππŽπŽπ‹π„π‘ 𝐎𝐍 πƒπŽπŒπ€πˆπ π‚πŽππ“π‘πŽπ‹π‹π„π‘π’

    Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί Watch my YouTube video bellow on how to disable Print Spooler on Domain Controllers πŸ‘‡ πŸ‘‡
    youtu.be/O80HHKdnbcQ

    #cswlrd #printspooler #domaincontrollers #printnightmare #videotutorial

  5. πŸ†• New blog post! "The PrintNightmare is not Over Yet"

    ℹ️ In this article, I take a look back at a previous post I wrote earlier this year about PrintNightmare. It turns out the Point and Print configuration I recommended at the end is still prone to Man-in-the-Middle attacks. So, I discuss that here, as well as additional mitigation I considered.

    Props to @parzel and @l4x4 who both reported this issue to me.

    πŸ‘‰ itm4n.github.io/printnightmare

    #printnightmare #windows #privesc #pentesting #pentest

  6. πŸ†• New blog post! "The PrintNightmare is not Over Yet"

    ℹ️ In this article, I take a look back at a previous post I wrote earlier this year about PrintNightmare. It turns out the Point and Print configuration I recommended at the end is still prone to Man-in-the-Middle attacks. So, I discuss that here, as well as additional mitigation I considered.

    Props to @parzel and @l4x4 who both reported this issue to me.

    πŸ‘‰ itm4n.github.io/printnightmare

    #printnightmare #windows #privesc #pentesting #pentest

  7. πŸ†• New blog post! "The PrintNightmare is not Over Yet"

    ℹ️ In this article, I take a look back at a previous post I wrote earlier this year about PrintNightmare. It turns out the Point and Print configuration I recommended at the end is still prone to Man-in-the-Middle attacks. So, I discuss that here, as well as additional mitigation I considered.

    Props to @parzel and @l4x4 who both reported this issue to me.

    πŸ‘‰ itm4n.github.io/printnightmare

    #printnightmare #windows #privesc #pentesting #pentest

  8. πŸ†• New blog post! "The PrintNightmare is not Over Yet"

    ℹ️ In this article, I take a look back at a previous post I wrote earlier this year about PrintNightmare. It turns out the Point and Print configuration I recommended at the end is still prone to Man-in-the-Middle attacks. So, I discuss that here, as well as additional mitigation I considered.

    Props to @parzel and @l4x4 who both reported this issue to me.

    πŸ‘‰ itm4n.github.io/printnightmare

    #printnightmare #windows #privesc #pentesting #pentest

  9. πŸ†• New blog post! "The PrintNightmare is not Over Yet"

    ℹ️ In this article, I take a look back at a previous post I wrote earlier this year about PrintNightmare. It turns out the Point and Print configuration I recommended at the end is still prone to Man-in-the-Middle attacks. So, I discuss that here, as well as additional mitigation I considered.

    Props to @parzel and @l4x4 who both reported this issue to me.

    πŸ‘‰ itm4n.github.io/printnightmare

    #printnightmare #windows #privesc #pentesting #pentest

  10. Another Hypetweet FAIL

    #CUPS vuln isnt exactly nothing. It's an rce vulnerability and is now exploitable. however it isnt #Printnightmare.

    Im firmly of the opinion that one should either fully disclose or coordinate disclosure of vulnerabilities.

    anything else just panics people, harms our ability to respond to real threats, and distracts from things that really matter.

    pick a lane.

    #Glassof0J #Infosec #Vulnerability #TVM

    youtu.be/WimG264WkXM

  11. Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 𝐏𝐚𝐭𝐫𝐞𝐨𝐧 (English)
    patreon.com/posts/how-to-disab

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π…π¨π«πžπ§ππ¨π«π¬ (Czech)
    forendors.cz/p/39ff110621ce2c6

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π‡πžπ«π¨π‘πžπ«π¨ (Czech)
    herohero.co/cswrld/post/bcerox

    πŸ‘Share, like, comment!

    #video #tutorial #cswrld #printspooler #printnightmare

  12. Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 𝐏𝐚𝐭𝐫𝐞𝐨𝐧 (English)
    patreon.com/posts/how-to-disab

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π…π¨π«πžπ§ππ¨π«π¬ (Czech)
    forendors.cz/p/39ff110621ce2c6

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π‡πžπ«π¨π‘πžπ«π¨ (Czech)
    herohero.co/cswrld/post/bcerox

    πŸ‘Share, like, comment!

    #video #tutorial #cswrld #printspooler #printnightmare

  13. Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 𝐏𝐚𝐭𝐫𝐞𝐨𝐧 (English)
    patreon.com/posts/how-to-disab

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π…π¨π«πžπ§ππ¨π«π¬ (Czech)
    forendors.cz/p/39ff110621ce2c6

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π‡πžπ«π¨π‘πžπ«π¨ (Czech)
    herohero.co/cswrld/post/bcerox

    πŸ‘Share, like, comment!

    #video #tutorial #cswrld #printspooler #printnightmare

  14. Print Spooler is a service that takes care of print management. This includes, but is not limited to, managing printer drivers, scheduling print jobs, etc.

    Print Spooler had a critical vulnerability in the past referred to as PrintNightmare (CVE-2021-34527). This vulnerability allowed attackers to execute code with administrator privileges.

    The Print Spooler vulnerability was patched promptly, so if you have updated systems, the immediate risk associated with PrintNightmare is no longer present. And for normal systems, it is usually not feasible to disable Print Spooler. It would make printing impossible, which is usually not desirable.

    But domain controllers are a critical part of Active Directory and need to be as secure as possible, which means blocking everything that is not needed. And you certainly should not need to print on domain controllers, so it’s a good idea to disable Print Spooler on domain controllers.

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 𝐏𝐚𝐭𝐫𝐞𝐨𝐧 (English)
    patreon.com/posts/how-to-disab

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π…π¨π«πžπ§ππ¨π«π¬ (Czech)
    forendors.cz/p/39ff110621ce2c6

    πŸ“Ί π–πšπ­πœπ‘ 𝐭𝐑𝐞 𝐫𝐞𝐜𝐨𝐫𝐝𝐒𝐧𝐠 𝐨𝐧 π‡πžπ«π¨π‘πžπ«π¨ (Czech)
    herohero.co/cswrld/post/bcerox

    πŸ‘Share, like, comment!

    #video #tutorial #cswrld #printspooler #printnightmare

  15. Happy Monday everyone!

    I am sifting through the Cisco Talos Intelligence Group "Year In Review" report that was recently published and highlighting some of the things that I found useful/interesting from my perspective.

    Top Targeted Vulnerabilities:
    7/10 of the top CVE's belonged to #Microsoft. Now I am not pointing fingers, I think it is there simply because the vast majority of environments are Windows.
    What IS concerning is that there are multiple vulnerabilities that were being exploited that were either 10 years old or ALMOST 10 years old.
    8/10 of the top CVE's had a score of 9 or above.

    One of these CVE's was CVE-2021-1675, which is a remote code execution vulnerability that exists when the Windows Print Spooler service improperly performs privileged file operations. One product of this vulnerability was the #PrintNightmare exploit that was leveraged by the #Magniber ransomware group.

    Stay tuned for more as we work our way through this report! Enjoy and Happy Hunting!

    blog.talosintelligence.com/tal

  16. Do you have Print Spooler enabled on your Domain Controllers? Do you know that the PrintNightmare critical vulnerability was related to the Print Spooler service?

    Print Spooler should be disabled on Domain Controllers completely. You can easily disable it via GPO. #cybersecurity #tip #ad #dc #printspooler #printnightmare cswrld.com/2023/12/how-to-disa

  17. Do you have Print Spooler enabled on your Domain Controllers? Do you know that the PrintNightmare critical vulnerability was related to the Print Spooler service?

    Print Spooler should be disabled on Domain Controllers completely. You can easily disable it via GPO. #cybersecurity #tip #ad #dc #printspooler #printnightmare cswrld.com/2023/12/how-to-disa

  18. Do you have Print Spooler enabled on your Domain Controllers? Do you know that the PrintNightmare critical vulnerability was related to the Print Spooler service?

    Print Spooler should be disabled on Domain Controllers completely. You can easily disable it via GPO. #cybersecurity #tip #ad #dc #printspooler #printnightmare cswrld.com/2023/12/how-to-disa

  19. Do you have Print Spooler enabled on your Domain Controllers? Do you know that the PrintNightmare critical vulnerability was related to the Print Spooler service?

    Print Spooler should be disabled on Domain Controllers completely. You can easily disable it via GPO. #cybersecurity #tip #ad #dc #printspooler #printnightmare cswrld.com/2023/12/how-to-disa

  20. Do you have Print Spooler enabled on your Domain Controllers? Do you know that the PrintNightmare critical vulnerability was related to the Print Spooler service?

    Print Spooler should be disabled on Domain Controllers completely. You can easily disable it via GPO. #cybersecurity #tip #ad #dc #printspooler #printnightmare cswrld.com/2023/12/how-to-disa

  21. Ich habe einen Hacker-Spickzettel geschrieben, den ich bei CTFs oder Pentests benutze: 1337.observer

    Neben kleineren Tricks, wie verschiedene Hackingtools verwendet werden, sind dort auch Anleitungen zu aktuellen, kritischen SicherheitslΓΌcken mit drin, wie #Log4Shell (Java), #PrintNightmare (Windows) oder #PwnKit (Linux).

    Die Datei ist natürlich noch am Anfang. Vielleicht hilft das ja noch jemanden außer mir.

  22. Seit Anfang September haben Angreifer eine Windows-LΓΌcke im Visier. Nun gibt es Sicherheitsupdates. Auch PrintNightmare spielt am Patchday nochmal eine Rolle.
    Patchday: Microsoft schließt von Angreifern ausgenutzte Lücke in Windows
  23. RT @[email protected]

    Great #patchtuesday Microsoft, but did you not forgot something for #printnightmare? πŸ€”

    Still SYSTEM from standard user...

    (I may have missed something, but #mimikatzπŸ₯mimispool library still loads... πŸ€·β€β™‚οΈ)

    πŸ¦πŸ”—: twitter.com/gentilkiwi/status/

  24. Angreifer kΓΆnnten viele Windows-Versionen attackieren und kompromittieren. Bislang gibt es keinen Patch. Admins mΓΌssen Systeme mit einem Workaround absichern. PrintNightmare: Schadcode-LΓΌcke in Windows bedroht ganze Netzwerke