101010.pl

BSIEuer Account wurde gehackt? Im Reel zeigen wir euch die ersten Schritte. 👉 Wie ihr langfristig eure Sicherheit stärkt und Schäden begrenzt, erfahrt ihr auf unserer Website: <a href="https://www.bsi.bund.de/dok/6700632" rel="nofollow noopener" translate="no" target="_blank">https://www.bsi.bund.de/dok/6700632</a> <a href="https://social.bund.de/tags/CyberHygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberHygiene</a> <a href="https://social.bund.de/tags/AccountSicherheit" class="mention hashtag" rel="nofollow noopener" target="_blank">#AccountSicherheit</a> <a href="https://social.bund.de/tags/DeutschlandDigitalSicherBSI" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeutschlandDigitalSicherBSI</a> <a href="https://social.bund.de/tags/2FA" class="mention hashtag" rel="nofollow noopener" target="_blank">#2FA</a> <a href="https://social.bund.de/tags/OnlineSchutz" class="mention hashtag" rel="nofollow noopener" target="_blank">#OnlineSchutz</a>

Erik van Straten<a href="https://infosec.exchange/@avoidthehack" class="u-url mention" rel="nofollow noopener" target="_blank">@avoidthehack</a> : MFA/2FA using text messages, voice or authenticator aps was broken in 2019 (as Alex Weinert, Director of Identity Security at Microsoft, told us in <a href="https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/all-your-creds-are-belong-to-us/ba-p/855124" rel="nofollow noopener" translate="no" target="_blank">https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/all-your-creds-are-belong-to-us/ba-p/855124</a>).When using a password manager (which is the least bad solution), there are things you should take care of and settings that can prevent most phishing attacks, as I wrote in <a href="https://infosec.exchange/@ErikvanStraten/113277630925350550" rel="nofollow noopener" translate="no" target="_blank">https://infosec.exchange/@ErikvanStraten/113277630925350550</a>.<a href="https://infosec.exchange/tags/PasswordManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#PasswordManager</a> <a href="https://infosec.exchange/tags/CheckHttps" class="mention hashtag" rel="nofollow noopener" target="_blank">#CheckHttps</a> <a href="https://infosec.exchange/tags/CheckDomainName" class="mention hashtag" rel="nofollow noopener" target="_blank">#CheckDomainName</a> <a href="https://infosec.exchange/tags/MakeBackups" class="mention hashtag" rel="nofollow noopener" target="_blank">#MakeBackups</a> <a href="https://infosec.exchange/tags/ProtectYourDevice" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProtectYourDevice</a> <a href="https://infosec.exchange/tags/CyberHygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberHygiene</a>

ENISAR to <a href="https://respublicae.eu/@enisa_eu" class="u-url mention" rel="nofollow noopener" target="_blank">@enisa_eu</a>: 🧐Take a look at our wagons🚃 and discover which are the <a href="https://respublicae.eu/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cybersecurity</a> habits that must be adopted to minimise cyber risks and protect data.Follow the tips from our Streetcar named <a href="https://respublicae.eu/tags/CyberHygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberHygiene</a>🚆<a href="https://respublicae.eu/tags/CyberOnTrack" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberOnTrack</a> 🐦🔗: <a href="https://nitter.cz/enisa_eu/status/1722634816913293445#m" rel="nofollow noopener" target="_blank">https://nitter.cz/enisa_eu/status/1722634816913293445#m</a>[2023-11-09 15:18 UTC]

🛡 H3lium@infosec.exchange/:~# :blinking_cursor:"Critical Alert! 🚨 Veeam ONE Monitor in the Crosshairs 🎯"Veeam ONE -a comprehensive monitoring and analytics solution that is part of the Veeam Backup & Replication suite- has issued a high alert 🛑, releasing hotfixes for four vulnerabilities in its Veeam ONE platform, with two critical risks scoring near the max on the CVSS scale (9.8/9.9). The most severe allows RCE and NTLM hash theft! Patch ASAP! 🛠️Less critical but still noteworthy, CVE-2023-38549 and CVE-2023-41723 show that even with less privileged roles, Veeam ONE users could exploit XSS attacks and view sensitive schedules. Keep those defenses up! 🏰Tags: <a href="https://infosec.exchange/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberSecurity</a> <a href="https://infosec.exchange/tags/Veeam" class="mention hashtag" rel="nofollow noopener" target="_blank">#Veeam</a> <a href="https://infosec.exchange/tags/RCE" class="mention hashtag" rel="nofollow noopener" target="_blank">#RCE</a> <a href="https://infosec.exchange/tags/Vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vulnerability</a> <a href="https://infosec.exchange/tags/PatchTuesday" class="mention hashtag" rel="nofollow noopener" target="_blank">#PatchTuesday</a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.exchange/tags/CyberThreat" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberThreat</a> <a href="https://infosec.exchange/tags/XSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#XSS</a> <a href="https://infosec.exchange/tags/Vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vulnerabilities</a> <a href="https://infosec.exchange/tags/DefenseInDepth" class="mention hashtag" rel="nofollow noopener" target="_blank">#DefenseInDepth</a> <a href="https://infosec.exchange/tags/CyberHygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberHygiene</a>CVE Details: <ul><li>CVE-2023-38547: Potential SQL RCE <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38547" rel="nofollow noopener" target="_blank">MITRE ATT&CK</a></li><li>CVE-2023-38548: NTLM hash theft <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38548" rel="nofollow noopener" target="_blank">MITRE ATT&CK</a></li><li>CVE-2023-38549: XSS requiring admin interaction <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38549" rel="nofollow noopener" target="_blank">MITRE ATT&CK</a></li><li>CVE-2023-41723: Schedule viewing without change permissions <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-41723" rel="nofollow noopener" target="_blank">MITRE ATT&CK</a></li></ul><a href="https://www.bleepingcomputer.com/news/security/veeam-warns-of-critical-bugs-in-veeam-one-monitoring-platform/" rel="nofollow noopener" target="_blank">Source</a> and <a href="https://www.veeam.com/kb4508" rel="nofollow noopener" target="_blank">Veeam Support Knowledge Base</a>

Craig NewmarkTaking a data-driven approach, @GlobalCyberAlln and @TidalCyber 's recent report validates the significant impact basic <a href="https://mastodon.social/tags/cyberhygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberhygiene</a> measures have in defense against the most relevant <a href="https://mastodon.social/tags/ransomware" class="mention hashtag" rel="nofollow noopener" target="_blank">#ransomware</a> methods of attack against <a href="https://mastodon.social/tags/SMBs" class="mention hashtag" rel="nofollow noopener" target="_blank">#SMBs</a>. Learn more at <a href="https://www.globalcyberalliance.org/reports_publications/defensive-measures-against-ransomware/" rel="nofollow noopener" translate="no" target="_blank">https://www.globalcyberalliance.org/reports_publications/defensive-measures-against-ransomware/</a>

🛡 H3lium@infosec.exchange/:~# :blinking_cursor:"🚨 curl Vulnerability Alert: SOCKS5 Heap Buffer Overflow 🚨"A critical heap buffer overflow vulnerability has been identified in <code>curl</code>, specifically in the SOCKS5 proxy handshake. When curl is instructed to pass the hostname to the SOCKS5 proxy for resolution, a hostname exceeding 255 bytes should trigger local name resolving. However, due to a bug, a slow SOCKS5 handshake might erroneously copy an overly long hostname to the target buffer instead of just the resolved address, causing a potential overflow. 🐛💻🔥This flaw, tagged as CVE-2023-38545, affects libcurl versions 7.69.0 to 8.3.0 and has been assigned a high severity rating. The vulnerability was introduced when the SOCKS5 handshake code transitioned from a blocking function to a non-blocking state machine. The issue has been resolved in curl version 8.4.0, and users are urged to upgrade or apply patches to mitigate risks. 🛡️🔄Source: <a href="https://curl.se/docs/CVE-2023-38545.html" rel="nofollow noopener" target="_blank">curl - CVE-2023-38545</a>Tags: <a href="https://infosec.exchange/tags/curl" class="mention hashtag" rel="nofollow noopener" target="_blank">#curl</a> <a href="https://infosec.exchange/tags/Vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vulnerability</a> <a href="https://infosec.exchange/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cybersecurity</a> <a href="https://infosec.exchange/tags/CVE202338545" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE202338545</a> <a href="https://infosec.exchange/tags/BufferOverflow" class="mention hashtag" rel="nofollow noopener" target="_blank">#BufferOverflow</a> <a href="https://infosec.exchange/tags/InfoSec" class="mention hashtag" rel="nofollow noopener" target="_blank">#InfoSec</a> <a href="https://infosec.exchange/tags/PatchManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#PatchManagement</a> <a href="https://infosec.exchange/tags/CyberHygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberHygiene</a>👥 Credits: Reported and patched by Jay Satiro. A heartfelt thanks to Jay for enhancing the security of the digital realm!🔗 <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-38545" rel="nofollow noopener" target="_blank">MITRE CVE-2023-38545</a>🛠️ Recommendations:<ol><li>Upgrade: Update curl to version 8.4.0 or a newer release where the issue is fixed.</li><li>Patch: If upgrading is not feasible, consider applying the provided patch to your local version of curl.</li><li>Proxy Configuration: Avoid using CURLPROXY_SOCKS5_HOSTNAME proxies with curl.</li><li>Environment Variables: Do not set proxy environment variables to socks5h://.</li></ol>

Dr. PattieA New View of Cyber Hygiene (pg. 171) <a href="https://mastodon.social/tags/MythAmerica" class="mention hashtag" rel="nofollow noopener" target="_blank">#MythAmerica</a> Click here to purchase: <a href="https://bit.ly/CyberMythsBook" rel="nofollow noopener" translate="no" target="_blank">https://bit.ly/CyberMythsBook</a>. <a href="https://mstdn.social/@spaf" class="u-url mention" rel="nofollow noopener" target="_blank">@spaf</a> <a href="https://infosec.exchange/@dykstra" class="u-url mention" rel="nofollow noopener" target="_blank">@dykstra</a> <a href="https://infosec.exchange/@theladyofgeek" class="u-url mention" rel="nofollow noopener" target="_blank">@theladyofgeek</a><a href="https://mastodon.social/tags/CybersecurityMythsAndMisconconceptions" class="mention hashtag" rel="nofollow noopener" target="_blank">#CybersecurityMythsAndMisconconceptions</a> <a href="https://mastodon.social/tags/CyberHygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberHygiene</a> <a href="https://mastodon.social/tags/WashYourDirtyBits" class="mention hashtag" rel="nofollow noopener" target="_blank">#WashYourDirtyBits</a> <a href="https://mastodon.social/tags/ColdWaterWash" class="mention hashtag" rel="nofollow noopener" target="_blank">#ColdWaterWash</a>

k3ym𖺀I wanted to share this absolutely brilliant info-graphic put out by <a href="https://infosec.exchange/tags/CISA" class="mention hashtag" rel="nofollow noopener" target="_blank">#CISA</a> about prioritization of the most impactful security measures you can implement. I love that they call out that we should be implementing the basics of cyber hygiene even before purchasing all of the cool flashy security tools:<ul><li>Implement MFA</li><li>Patch Management</li><li>Backups</li><li>Minimize Attack Surface</li><li>Have (and test) your IR plan</li><li>Security awareness training</li></ul>All of the above can be achieved without investing in EDR/XDR, SIEM, SOAR, sandbox, etc. <a href="https://infosec.exchange/tags/backtothebasics" class="mention hashtag" rel="nofollow noopener" target="_blank">#backtothebasics</a> <a href="https://infosec.exchange/tags/cyberhygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberhygiene</a>

Geekmaster 👽:system76:<a href="https://infosec.exchange/@jerry" class="u-url mention" rel="nofollow noopener" target="_blank">@jerry</a> I believe this is an <a href="https://ioc.exchange/tags/InheritRisk" class="mention hashtag" rel="nofollow noopener" target="_blank">#InheritRisk</a> working in the <a href="https://ioc.exchange/tags/EnterpriseSpace" class="mention hashtag" rel="nofollow noopener" target="_blank">#EnterpriseSpace</a>, especially the <a href="https://ioc.exchange/tags/FediSpace" class="mention hashtag" rel="nofollow noopener" target="_blank">#FediSpace</a> (regardless of which country you work in). While this sucks generally, it appears on the surface that this could have been avoided by simply installing AV updates? That's <a href="https://ioc.exchange/tags/Security101" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security101</a>. Especially after they were already attacked. <a href="https://ioc.exchange/tags/ShouldHaveKnownBetter" class="mention hashtag" rel="nofollow noopener" target="_blank">#ShouldHaveKnownBetter</a>. Not too comfortable with a 7-year jail sentence, but without knowing their local laws around this topic I can't really speak to that in depth.It is another hard example of why regular <a href="https://ioc.exchange/tags/Patching" class="mention hashtag" rel="nofollow noopener" target="_blank">#Patching</a> and <a href="https://ioc.exchange/tags/SystemUpdates" class="mention hashtag" rel="nofollow noopener" target="_blank">#SystemUpdates</a> are essential - at work and especially at home. Even if they are manually applied! It's not just good <a href="https://ioc.exchange/tags/CyberHygiene" class="mention hashtag" rel="nofollow noopener" target="_blank">#CyberHygiene</a>, in many instances it is a regulatory or <a href="https://ioc.exchange/tags/LegalRequirement" class="mention hashtag" rel="nofollow noopener" target="_blank">#LegalRequirement</a>.<a href="https://ioc.exchange/tags/HugYourInfosecTeam" class="mention hashtag" rel="nofollow noopener" target="_blank">#HugYourInfosecTeam</a> 😬

Recent searches

Search options

Administered by:

Server stats:

#cyberhygiene