Med-Mastodon

xoron :verified:File encryption with a browser.I've been exploring the <a href="https://infosec.exchange/tags/WebCryptoAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebCryptoAPI</a> and I'm impressed!When combined with the <a href="https://infosec.exchange/tags/FileSystemAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystemAPI</a>, it offers a seemingly secure way to <a href="https://infosec.exchange/tags/encrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypt</a> and <a href="https://infosec.exchange/tags/store" class="mention hashtag" rel="nofollow noopener" target="_blank">#store</a> files directly on your device. Think <a href="https://infosec.exchange/tags/localstorage" class="mention hashtag" rel="nofollow noopener" target="_blank">#localstorage</a>, but with <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a>!I know <a href="https://infosec.exchange/tags/webapps" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapps</a> can have <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> vulnerabilities since the code is served over the web, so I've <a href="https://infosec.exchange/tags/OpenSourced" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSourced</a> my demo! You can check it out, and it should even work if <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> on <a href="https://infosec.exchange/tags/GitHubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHubPages</a>.Live Demo: <a href="https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo" rel="nofollow noopener" translate="no" target="_blank">https://dim.positive-intentions.com/?path=/story/usefs--encrypted-demo</a>Demo Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/stories/05-Hooks-useFS.stories.js</a>Hook Code: <a href="https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim/blob/staging/src/hooks/useFS.js</a>IMPORTANT NOTES (PLEASE READ!): * This is NOT a product. It's for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demonstration" class="mention hashtag" rel="nofollow noopener" target="_blank">#demonstration</a> purposes only. * It has NOT been reviewed or audited. Do NOT use for sensitive data. * The "password encryption" currently uses a hardcoded password. This is for demonstration, not security. * This is NOT meant to replace robust solutions like <a href="https://infosec.exchange/tags/VeraCrypt" class="mention hashtag" rel="nofollow noopener" target="_blank">#VeraCrypt</a>. It's just a <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> to show what's possible with <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> <a href="https://infosec.exchange/tags/APIs" class="mention hashtag" rel="nofollow noopener" target="_blank">#APIs</a>.<a href="https://infosec.exchange/tags/Encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#Encryption</a> <a href="https://infosec.exchange/tags/Cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cryptography</a> <a href="https://infosec.exchange/tags/JavaScript" class="mention hashtag" rel="nofollow noopener" target="_blank">#JavaScript</a> <a href="https://infosec.exchange/tags/Frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#Frontend</a> <a href="https://infosec.exchange/tags/Privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Privacy</a> <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a> <a href="https://infosec.exchange/tags/WebDevelopment" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebDevelopment</a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://infosec.exchange/tags/Developer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Developer</a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://infosec.exchange/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://infosec.exchange/tags/GitHub" class="mention hashtag" rel="nofollow noopener" target="_blank">#GitHub</a> <a href="https://infosec.exchange/tags/MastodonDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#MastodonDev</a> <a href="https://infosec.exchange/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://infosec.exchange/tags/WebStandards" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebStandards</a> <a href="https://infosec.exchange/tags/FileSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#FileSystem</a> <a href="https://infosec.exchange/tags/WebAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebAPI</a> <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a>

xoron :verified:React-like functional webcomponents, but with vanilla HTML, JS and CSSIntroducing Dim – a new <a href="https://infosec.exchange/tags/Framework" class="mention hashtag" rel="nofollow noopener" target="_blank">#Framework</a> that brings <a href="https://infosec.exchange/tags/ReactJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReactJS</a>-like functional <a href="https://infosec.exchange/tags/JSX" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSX</a>-syntax with <a href="https://infosec.exchange/tags/VanillaJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#VanillaJS</a>. Check it out here: 🔗 Project: <a href="https://github.com/positive-intentions/dim" rel="nofollow noopener" translate="no" target="_blank">https://github.com/positive-intentions/dim</a> 🔗 Website: <a href="https://dim.positive-intentions.com" rel="nofollow noopener" translate="no" target="_blank">https://dim.positive-intentions.com</a>My journey with <a href="https://infosec.exchange/tags/WebComponents" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebComponents</a> started with Lit, and while I appreciated its native browser support (less <a href="https://infosec.exchange/tags/Tooling" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tooling</a>!), coming from <a href="https://infosec.exchange/tags/ReactJS" class="mention hashtag" rel="nofollow noopener" target="_blank">#ReactJS</a>, the class components felt like a step backward. The <a href="https://infosec.exchange/tags/FunctionalProgramming" class="mention hashtag" rel="nofollow noopener" target="_blank">#FunctionalProgramming</a> approach in React significantly improved my <a href="https://infosec.exchange/tags/DeveloperExperience" class="mention hashtag" rel="nofollow noopener" target="_blank">#DeveloperExperience</a> and debugging flow.So, I set out to build a thin, functional wrapper around <a href="https://infosec.exchange/tags/Lit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Lit</a>, and Dim is the result! It's a <a href="https://infosec.exchange/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> right now, with "main" <a href="https://infosec.exchange/tags/Hooks" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hooks</a> similar to React, plus some custom ones like useStore for <a href="https://infosec.exchange/tags/EncryptionAtRest" class="mention hashtag" rel="nofollow noopener" target="_blank">#EncryptionAtRest</a>. (Note: <a href="https://infosec.exchange/tags/StateManagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#StateManagement</a> for encryption-at-rest is still unstable and currently uses a hardcoded password while I explore <a href="https://infosec.exchange/tags/Passwordless" class="mention hashtag" rel="nofollow noopener" target="_blank">#Passwordless</a> options like <a href="https://infosec.exchange/tags/WebAuthn" class="mention hashtag" rel="nofollow noopener" target="_blank">#WebAuthn</a>/#Passkeys).You can dive deeper into the <a href="https://infosec.exchange/tags/Documentation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Documentation</a> and see how it works here: 📚 Dim Docs: <a href="https://positive-intentions.com/docs/category/dim" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/docs/category/dim</a>This <a href="https://infosec.exchange/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> project is still in its early stages and very <a href="https://infosec.exchange/tags/Unstable" class="mention hashtag" rel="nofollow noopener" target="_blank">#Unstable</a>, so expect <a href="https://infosec.exchange/tags/BreakingChanges" class="mention hashtag" rel="nofollow noopener" target="_blank">#BreakingChanges</a>. I've already received valuable <a href="https://infosec.exchange/tags/Feedback" class="mention hashtag" rel="nofollow noopener" target="_blank">#Feedback</a> on some functions regarding <a href="https://infosec.exchange/tags/Security" class="mention hashtag" rel="nofollow noopener" target="_blank">#Security</a>, and I'm actively investigating those. I'm genuinely open to all feedback as I continue to develop it!<a href="https://infosec.exchange/tags/FrontendDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#FrontendDev</a> <a href="https://infosec.exchange/tags/JSFramework" class="mention hashtag" rel="nofollow noopener" target="_blank">#JSFramework</a> <a href="https://infosec.exchange/tags/Innovation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Innovation</a> <a href="https://infosec.exchange/tags/Coding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Coding</a> <a href="https://infosec.exchange/tags/Programmer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programmer</a> <a href="https://infosec.exchange/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a>

Kevin Karhan :verified:<a href="https://mastodon.social/@mrgrumpymonkey" class="u-url mention" rel="nofollow noopener" target="_blank">@mrgrumpymonkey</a> it is.One can repartition Windows installations on the fly whilst running (and even then there are tools like <a href="https://infosec.space/tags/Wubi" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wubi</a> that made it easy to setup <a href="https://infosec.space/tags/dualboot" class="mention hashtag" rel="nofollow noopener" target="_blank">#dualboot</a> <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> & <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a>.<ul><li>ISOLINUX does allow for "load image into RAM and boot" setups. I literally use that on <a href="https://infosec.space/@OS1337" class="u-url mention" rel="nofollow noopener" target="_blank">@OS1337</a> because no system that can boot it will have > 16 MB RAM anyway ( 8 MB is the hard limit for bare linux kernel) so merely making Windows' bootloader to chainload <a href="https://infosec.space/tags/isolinux" class="mention hashtag" rel="nofollow noopener" target="_blank">#isolinux</a> to load that image in RAM and yeet it isn't out of the question.</li></ul>I just have neither a <a href="https://infosec.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> machine nor time and spoons to make such a tool, much less to basically create even said <a href="https://infosec.space/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> "<a href="https://infosec.space/tags/Malware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Malware</a>"…<ul><li>But thanks to <a href="https://infosec.space/tags/GoldenKeyBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#GoldenKeyBoot</a>, <a href="https://infosec.space/tags/CensorBoot" class="mention hashtag" rel="nofollow noopener" target="_blank">#CensorBoot</a> is unfixably insecure!</li></ul>

Matasoft🧪 Not sure if AI-powered spreadsheets are right for you? Start with a proof of concept! Download (Un)Perplexed Spready, request a free evaluation period, and test it on your actual data challenges. See the transformation firsthand before committing! 🔍 <a href="https://mstdn.business/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> <a href="https://mstdn.business/tags/TryBeforeBuy" class="mention hashtag" rel="nofollow noopener" target="_blank">#TryBeforeBuy</a> <a href="https://matasoft.hr/qtrendcontrol/index.php/un-perplexed-spready/un-perplexed-spready-download" rel="nofollow noopener" translate="no" target="_blank">https://matasoft.hr/qtrendcontrol/index.php/un-perplexed-spready/un-perplexed-spready-download</a>

VarietyProof of Concept Filmmakers Debut at L.A. Showcase: ‘These Helmers Can Start Shaping and Remaking the Industry,’ Says Cate Blanchett <a href="https://mastodon.social/tags/Variety" class="mention hashtag" rel="nofollow noopener" target="_blank">#Variety</a> <a href="https://mastodon.social/tags/Events" class="mention hashtag" rel="nofollow noopener" target="_blank">#Events</a> <a href="https://mastodon.social/tags/News" class="mention hashtag" rel="nofollow noopener" target="_blank">#News</a> <a href="https://mastodon.social/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a><a href="https://variety.com/2025/artisans/news/cate-blanchett-proof-of-concept-short-films-la-showcase-1236382766/" rel="nofollow noopener" translate="no" target="_blank">https://variety.com/2025/artisans/news/cate-blanchett-proof-of-concept-short-films-la-showcase-1236382766/</a>

AlessandroSto portando avanti il progetto immich-fuse... Funziona! 🚀 <a href="https://alorenzi.eu/2025/04/13/immich-fuse.html?v1" rel="nofollow noopener" translate="no" target="_blank">https://alorenzi.eu/2025/04/13/immich-fuse.html?v1</a><a href="https://livellosegreto.it/tags/immich" class="mention hashtag" rel="nofollow noopener" target="_blank">#immich</a> <a href="https://livellosegreto.it/tags/python" class="mention hashtag" rel="nofollow noopener" target="_blank">#python</a> <a href="https://livellosegreto.it/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://livellosegreto.it/tags/development" class="mention hashtag" rel="nofollow noopener" target="_blank">#development</a> <a href="https://livellosegreto.it/tags/POC" class="mention hashtag" rel="nofollow noopener" target="_blank">#POC</a> <a href="https://livellosegreto.it/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a>

Su_G<a href="https://sauropods.win/@futurebird" class="u-url mention" rel="nofollow noopener" target="_blank">@futurebird</a> You've convinced me! Bringing back extinct lichen is a great way to do proof of concept for bringing back extinct organisms, 🙂 <a href="https://aus.social/tags/proofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofOfConcept</a> <a href="https://aus.social/tags/lichen" class="mention hashtag" rel="nofollow noopener" target="_blank">#lichen</a> <a href="https://aus.social/tags/Extinct" class="mention hashtag" rel="nofollow noopener" target="_blank">#Extinct</a>

Die Kehrseite - UpSideDownGib niemals einem kleinen Geist Macht über ein großes Land.<a href="https://mastodon.social/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a>

Kevin Veen-Birkenbach💡 Today, I built a Proof of Concept: a dynamic cryptocurrency miner! The idea was to use idle hardware resources to mine crypto. 🖥️💰BUT... after some testing, I realized it's not worth it in Germany due to high energy costs ⚡ and low crypto prices 📉.Check it out here (but I don’t recommend using it 😉): <a href="https://github.com/kevinveenbirkenbach/dynamic-miner" rel="nofollow noopener" translate="no" target="_blank">https://github.com/kevinveenbirkenbach/dynamic-miner</a><a href="https://microblog.veen.world/tags/CryptoMining" class="mention hashtag" rel="nofollow noopener" target="_blank">#CryptoMining</a> <a href="https://microblog.veen.world/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> <a href="https://microblog.veen.world/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a> <a href="https://microblog.veen.world/tags/TechExperiments" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechExperiments</a> <a href="https://microblog.veen.world/tags/DynamicMiner" class="mention hashtag" rel="nofollow noopener" target="_blank">#DynamicMiner</a> <a href="https://microblog.veen.world/tags/EnergyCosts" class="mention hashtag" rel="nofollow noopener" target="_blank">#EnergyCosts</a> <a href="https://microblog.veen.world/tags/CryptoPrices" class="mention hashtag" rel="nofollow noopener" target="_blank">#CryptoPrices</a> <a href="https://microblog.veen.world/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> <a href="https://microblog.veen.world/tags/ETC" class="mention hashtag" rel="nofollow noopener" target="_blank">#ETC</a> <a href="https://microblog.veen.world/tags/BTC" class="mention hashtag" rel="nofollow noopener" target="_blank">#BTC</a> <a href="https://microblog.veen.world/tags/Bitcoin" class="mention hashtag" rel="nofollow noopener" target="_blank">#Bitcoin</a> <a href="https://microblog.veen.world/tags/Docker" class="mention hashtag" rel="nofollow noopener" target="_blank">#Docker</a> <a href="https://microblog.veen.world/tags/Currency" class="mention hashtag" rel="nofollow noopener" target="_blank">#Currency</a> <a href="https://microblog.veen.world/tags/Crypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#Crypto</a>

xoron :verified:<a href="https://positive-intentions.com/blog/introducing-decentralized-chat" rel="nofollow noopener" translate="no" target="_blank">https://positive-intentions.com/blog/introducing-decentralized-chat</a>id like to share some details about how my app works so you can discover/give me feedback on my app. id like to have wording in my app to say something like "most secure chat app in the world"... i probably cant do that because it doesnt qualify.im not an expert on <a href="https://infosec.exchange/tags/cyberSecurity" class="mention hashtag" rel="nofollow noopener" target="_blank">#cyberSecurity</a>. im sure there are many gaps in my knowlege in this domain.using <a href="https://infosec.exchange/tags/javascript" class="mention hashtag" rel="nofollow noopener" target="_blank">#javascript</a>, i initially created a fairly basic <a href="https://infosec.exchange/tags/chatApp" class="mention hashtag" rel="nofollow noopener" target="_blank">#chatApp</a> using using <a href="https://infosec.exchange/tags/peerjs" class="mention hashtag" rel="nofollow noopener" target="_blank">#peerjs</a> to create <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypted</a> <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#webrtc</a> <a href="https://infosec.exchange/tags/connections" class="mention hashtag" rel="nofollow noopener" target="_blank">#connections</a>. this was then easily enhanced by exchanging additional <a href="https://infosec.exchange/tags/encryption" class="mention hashtag" rel="nofollow noopener" target="_blank">#encryption</a> <a href="https://infosec.exchange/tags/keys" class="mention hashtag" rel="nofollow noopener" target="_blank">#keys</a> from <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> functions built into browsers (<a href="https://infosec.exchange/tags/webcrypto" class="mention hashtag" rel="nofollow noopener" target="_blank">#webcrypto</a> api) to add a redundent layer of encryption. a <a href="https://infosec.exchange/tags/diffieHelman" class="mention hashtag" rel="nofollow noopener" target="_blank">#diffieHelman</a> key <a href="https://infosec.exchange/tags/exchange" class="mention hashtag" rel="nofollow noopener" target="_blank">#exchange</a> is done over <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#webrtc</a> (which can be considered <a href="https://infosec.exchange/tags/secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#secure</a> when exchanged over public channels) to create <a href="https://infosec.exchange/tags/serverless" class="mention hashtag" rel="nofollow noopener" target="_blank">#serverless</a> <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> <a href="https://infosec.exchange/tags/authentication" class="mention hashtag" rel="nofollow noopener" target="_blank">#authentication</a>.- i sometimes recieve feedback like "javascript is inherently insecure". i disagree with this and have <a href="https://infosec.exchange/tags/openedSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#openedSource</a> my <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> module. its basically a thin wrapper around vanilla cryptography functions of a <a href="https://infosec.exchange/tags/browser" class="mention hashtag" rel="nofollow noopener" target="_blank">#browser</a> (webcrypto api).- another concern for my kind of app (<a href="https://infosec.exchange/tags/PWA" class="mention hashtag" rel="nofollow noopener" target="_blank">#PWA</a>) is that the developer may introduce malicious code. this is an important point for which i open sourced the project and give instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a>. selhosting this app has some unique features. unlike many other <a href="https://infosec.exchange/tags/selfhosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosted</a> <a href="https://infosec.exchange/tags/projects" class="mention hashtag" rel="nofollow noopener" target="_blank">#projects</a>, this app can be hosted on <a href="https://infosec.exchange/tags/githubPages" class="mention hashtag" rel="nofollow noopener" target="_blank">#githubPages</a> (instructions are provided in the readme). im also working towards having better support for running the index.html directly without a static server.- to prevent things like browser extensions, the app uses strict <a href="https://infosec.exchange/tags/CSP" class="mention hashtag" rel="nofollow noopener" target="_blank">#CSP</a> headers to prevent <a href="https://infosec.exchange/tags/unauthorised" class="mention hashtag" rel="nofollow noopener" target="_blank">#unauthorised</a> code from running. <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> users should take note of this when setting up their own instance.- i received feedback the <a href="https://infosec.exchange/tags/Signal" class="mention hashtag" rel="nofollow noopener" target="_blank">#Signal</a>/#Simplex protocol is great. completely undertsandable and agree, but wonder if im reducing the <a href="https://infosec.exchange/tags/complexity" class="mention hashtag" rel="nofollow noopener" target="_blank">#complexity</a> by working with <a href="https://infosec.exchange/tags/webrtc" class="mention hashtag" rel="nofollow noopener" target="_blank">#webrtc</a>. while it has its many flaws, i think risks can be reasonable mitigated if the <a href="https://infosec.exchange/tags/cryptography" class="mention hashtag" rel="nofollow noopener" target="_blank">#cryptography</a> functions are implemented correctly. (all data out is <a href="https://infosec.exchange/tags/encrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#encrypted</a> and all data in is <a href="https://infosec.exchange/tags/decrypted" class="mention hashtag" rel="nofollow noopener" target="_blank">#decrypted</a> on-the-fly)- the key detail that makes this approach unique, is because as a <a href="https://infosec.exchange/tags/webapp" class="mention hashtag" rel="nofollow noopener" target="_blank">#webapp</a>, unlike other solutions, users have a choice of using any <a href="https://infosec.exchange/tags/device" class="mention hashtag" rel="nofollow noopener" target="_blank">#device</a>/#os/#browser. while a webapp can have nuanced <a href="https://infosec.exchange/tags/vulnerabilities" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerabilities</a>, i think by <a href="https://infosec.exchange/tags/openSourcing" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSourcing</a> and providing instructions for <a href="https://infosec.exchange/tags/selfhosting" class="mention hashtag" rel="nofollow noopener" target="_blank">#selfhosting</a> and instructions to <a href="https://infosec.exchange/tags/build" class="mention hashtag" rel="nofollow noopener" target="_blank">#build</a> for various <a href="https://infosec.exchange/tags/platforms" class="mention hashtag" rel="nofollow noopener" target="_blank">#platforms</a>, it can provide a reasonable level of <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>.i think if i stick to the principle of avoiding using any kind of "required" service provider (myself included) and allowing the <a href="https://infosec.exchange/tags/frontend" class="mention hashtag" rel="nofollow noopener" target="_blank">#frontend</a> and the peerjs-server to be <a href="https://infosec.exchange/tags/hosted" class="mention hashtag" rel="nofollow noopener" target="_blank">#hosted</a> <a href="https://infosec.exchange/tags/independently" class="mention hashtag" rel="nofollow noopener" target="_blank">#independently</a>, im on track for creating a <a href="https://infosec.exchange/tags/chatSystem" class="mention hashtag" rel="nofollow noopener" target="_blank">#chatSystem</a> with the "fewest moving parts". i hope you will agree this is true <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> and i hope i can use this as a step towards true <a href="https://infosec.exchange/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#privacy</a> and <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a>. <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> might be further improved by using a trusted <a href="https://infosec.exchange/tags/VPN" class="mention hashtag" rel="nofollow noopener" target="_blank">#VPN</a>.while there are several similar apps out there like mine. i think mine is distinctly a different approach. so its hard to find <a href="https://infosec.exchange/tags/bestPractices" class="mention hashtag" rel="nofollow noopener" target="_blank">#bestPractices</a> for the functionalities i want to achieve. in particular <a href="https://infosec.exchange/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#security</a> practices to use when using <a href="https://infosec.exchange/tags/p2p" class="mention hashtag" rel="nofollow noopener" target="_blank">#p2p</a> technology.(note: this app is an <a href="https://infosec.exchange/tags/unstable" class="mention hashtag" rel="nofollow noopener" target="_blank">#unstable</a>, <a href="https://infosec.exchange/tags/experiment" class="mention hashtag" rel="nofollow noopener" target="_blank">#experiment</a>, <a href="https://infosec.exchange/tags/proofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofOfConcept</a> and not ready to replace any other app or service. It's far from finished and provided for <a href="https://infosec.exchange/tags/testing" class="mention hashtag" rel="nofollow noopener" target="_blank">#testing</a> and <a href="https://infosec.exchange/tags/demo" class="mention hashtag" rel="nofollow noopener" target="_blank">#demo</a> purposes only. This post is to get <a href="https://infosec.exchange/tags/feedback" class="mention hashtag" rel="nofollow noopener" target="_blank">#feedback</a> on the progress to determine if i'm going in the right direction for a secure chat app)

Tino Eberl<a href="https://mastodon.online/tags/KINews" class="mention hashtag" rel="nofollow noopener" target="_blank">#KINews</a><a href="https://mastodon.online/tags/Gartner" class="mention hashtag" rel="nofollow noopener" target="_blank">#Gartner</a> prognostiziert, dass 30 % der generativen <a href="https://mastodon.online/tags/KIProjekte" class="mention hashtag" rel="nofollow noopener" target="_blank">#KIProjekte</a> nach dem <a href="https://mastodon.online/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a> (PoC) abgebrochen werden. Aber das ist nicht unbedingt schlecht: Ein <a href="https://mastodon.online/tags/PoC" class="mention hashtag" rel="nofollow noopener" target="_blank">#PoC</a> ermöglicht es Unternehmen, <a href="https://mastodon.online/tags/Risiken" class="mention hashtag" rel="nofollow noopener" target="_blank">#Risiken</a> und <a href="https://mastodon.online/tags/Machbarkeit" class="mention hashtag" rel="nofollow noopener" target="_blank">#Machbarkeit</a> frühzeitig zu bewerten, <a href="https://mastodon.online/tags/Kosten" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kosten</a> zu sparen und wertvolle Erfahrungen zu sammeln. So lassen sich ineffiziente Projekte stoppen, bevor sie teurer werden. Fazit: Ausprobieren lohnt sich und Abbrechen ist manchmal der bessere Weg. <a href="https://mastodon.online/tags/KI" class="mention hashtag" rel="nofollow noopener" target="_blank">#KI</a> <a href="https://mastodon.online/tags/Projektmanagement" class="mention hashtag" rel="nofollow noopener" target="_blank">#Projektmanagement</a><a href="https://tino-eberl.de/ki-news/gartner-30-der-ki-projekte-werden-nach-poc-abgebrochen-ja-gut-so/" rel="nofollow noopener" translate="no" target="_blank">https://tino-eberl.de/ki-news/gartner-30-der-ki-projekte-werden-nach-poc-abgebrochen-ja-gut-so/</a>

scops<a href="https://social.panic.com/@panic" class="u-url mention" rel="nofollow noopener" target="_blank">@panic</a> <a href="https://social.tchncs.de/tags/Audion" class="mention hashtag" rel="nofollow noopener" target="_blank">#Audion</a> (Viewer) as <a href="https://social.tchncs.de/tags/AppleMusic" class="mention hashtag" rel="nofollow noopener" target="_blank">#AppleMusic</a> controller is just awesome!There is a github repo with some basic changes need to do to make it work: <a href="https://github.com/zydeco/audion/tree/applescript" rel="nofollow noopener" translate="no" target="_blank">https://github.com/zydeco/audion/tree/applescript</a>I build my self a version based on the lastest sources (<a href="https://gitlab.com/panicinc/audion" rel="nofollow noopener" translate="no" target="_blank">https://gitlab.com/panicinc/audion</a>).Sadly there are a few bugs. For example: - The scrolling song title breaks out - The interface settings dialog doesn’t work - it’s just a placeholder<a href="https://social.tchncs.de/tags/mp3player" class="mention hashtag" rel="nofollow noopener" target="_blank">#mp3player</a> <a href="https://social.tchncs.de/tags/musicplayer" class="mention hashtag" rel="nofollow noopener" target="_blank">#musicplayer</a> <a href="https://social.tchncs.de/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> <a href="https://social.tchncs.de/tags/retro" class="mention hashtag" rel="nofollow noopener" target="_blank">#retro</a> <a href="https://social.tchncs.de/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a>

Kevin Karhan :verified:<a href="https://tilde.zone/@lunch" class="u-url mention" rel="nofollow noopener" target="_blank">@lunch</a> So you just admitted that you vomitted <a href="https://infosec.space/tags/FUD" class="mention hashtag" rel="nofollow noopener" target="_blank">#FUD</a> into my mentions without evidence?If you're so smart, then why don't you sell your <a href="https://infosec.space/tags/exploit" class="mention hashtag" rel="nofollow noopener" target="_blank">#exploit</a> / <a href="https://infosec.space/tags/ProofOfConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofOfConcept</a> / <a href="https://infosec.space/tags/Whitepaper" class="mention hashtag" rel="nofollow noopener" target="_blank">#Whitepaper</a> to the highest bidder?<ul><li>I'm shure <a href="https://infosec.space/tags/Zerodium" class="mention hashtag" rel="nofollow noopener" target="_blank">#Zerodium</a> and all the LEAs would try to outbid each other...</li></ul>Alas, your messages are just hot air, and not substantiated by anything...At best your info is <a href="https://www.youtube.com/watch?v=-3BF_mE2e6M" rel="nofollow noopener" target="_blank">2+ years outdated</a>...

Susan Larson ♀️🏳️‍🌈🏳️‍⚧️🌈<a href="https://mastodon.online/tags/CateBlanchett" class="mention hashtag" rel="nofollow noopener" target="_blank">#CateBlanchett</a> Is <a href="https://mastodon.online/tags/Pushing" class="mention hashtag" rel="nofollow noopener" target="_blank">#Pushing</a> for More <a href="https://mastodon.online/tags/Funding" class="mention hashtag" rel="nofollow noopener" target="_blank">#Funding</a> for <a href="https://mastodon.online/tags/Women" class="mention hashtag" rel="nofollow noopener" target="_blank">#Women</a> and <a href="https://mastodon.online/tags/LGBTQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#LGBTQ</a> <a href="https://mastodon.online/tags/Filmmakers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Filmmakers</a>, but She Wants to Know Why Nobody Asks <a href="https://mastodon.online/tags/Men" class="mention hashtag" rel="nofollow noopener" target="_blank">#Men</a> How to Fix ItThe <a href="https://mastodon.online/tags/Oscar" class="mention hashtag" rel="nofollow noopener" target="_blank">#Oscar</a>-<a href="https://mastodon.online/tags/winning" class="mention hashtag" rel="nofollow noopener" target="_blank">#winning</a> <a href="https://mastodon.online/tags/actor" class="mention hashtag" rel="nofollow noopener" target="_blank">#actor</a> was joined at <a href="https://mastodon.online/tags/Cannes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cannes</a> by her <a href="https://mastodon.online/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a> <a href="https://mastodon.online/tags/cofounders" class="mention hashtag" rel="nofollow noopener" target="_blank">#cofounders</a> <a href="https://mastodon.online/tags/CocoFrancini" class="mention hashtag" rel="nofollow noopener" target="_blank">#CocoFrancini</a> and Dr. <a href="https://mastodon.online/tags/StacySmith" class="mention hashtag" rel="nofollow noopener" target="_blank">#StacySmith</a> <a href="https://mastodon.online/tags/Women" class="mention hashtag" rel="nofollow noopener" target="_blank">#Women</a> <a href="https://mastodon.online/tags/Transgender" class="mention hashtag" rel="nofollow noopener" target="_blank">#Transgender</a> <a href="https://mastodon.online/tags/LGBTQ" class="mention hashtag" rel="nofollow noopener" target="_blank">#LGBTQ</a> <a href="https://mastodon.online/tags/LGBTQIA" class="mention hashtag" rel="nofollow noopener" target="_blank">#LGBTQIA</a> <a href="https://mastodon.online/tags/Entertainment" class="mention hashtag" rel="nofollow noopener" target="_blank">#Entertainment</a> <a href="https://mastodon.online/tags/Movies" class="mention hashtag" rel="nofollow noopener" target="_blank">#Movies</a> <a href="https://mastodon.online/tags/Representation" class="mention hashtag" rel="nofollow noopener" target="_blank">#Representation</a> <a href="https://mastodon.online/tags/Culture" class="mention hashtag" rel="nofollow noopener" target="_blank">#Culture</a> <a href="https://variety.com/2024/film/markets-festivals/cate-blanchett-women-lgbtq-filmmakers-proof-of-concept-cannes-1236010112/" rel="nofollow noopener" translate="no" target="_blank">https://variety.com/2024/film/markets-festivals/cate-blanchett-women-lgbtq-filmmakers-proof-of-concept-cannes-1236010112/</a>

Not SimonPalo Alto Networks released additional details about CVE-2024-3400: the fact that it is a combination of two bugs in PAN-OS; how an attacker was exploiting it; how disabling telemetry initially worked; and how they fixed it. The timeline from discovery to remediation encompasses the whole blog post. Overall a comprehensive after-action review from a company that notified the public almost immediately of an exploited zero-day. 🔗<a href="https://www.paloaltonetworks.com/blog/2024/04/more-on-the-pan-os-cve/" rel="nofollow noopener" translate="no" target="_blank">https://www.paloaltonetworks.com/blog/2024/04/more-on-the-pan-os-cve/</a><a href="https://infosec.exchange/tags/CVE_2024_3400" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_3400</a> <a href="https://infosec.exchange/tags/PaloAltoNetworks" class="mention hashtag" rel="nofollow noopener" target="_blank">#PaloAltoNetworks</a> <a href="https://infosec.exchange/tags/zeroday" class="mention hashtag" rel="nofollow noopener" target="_blank">#zeroday</a> <a href="https://infosec.exchange/tags/activeexploitation" class="mention hashtag" rel="nofollow noopener" target="_blank">#activeexploitation</a> <a href="https://infosec.exchange/tags/eitw" class="mention hashtag" rel="nofollow noopener" target="_blank">#eitw</a> <a href="https://infosec.exchange/tags/kev" class="mention hashtag" rel="nofollow noopener" target="_blank">#kev</a> <a href="https://infosec.exchange/tags/KnownExploitedVulnerabilitiesCatalog" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnownExploitedVulnerabilitiesCatalog</a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerability</a> <a href="https://infosec.exchange/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a> <a href="https://infosec.exchange/tags/PANOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#PANOS</a> <a href="https://infosec.exchange/tags/IOC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IOC</a>

Not SimonZscaler observed exploitation of the Palo Alto Networks PAN-OS command injection zero-day vulnerability CVE-2024-3400 following the release of the PoC exploit code. Zscaler provides an attack flow diagram, and a technical analysis of the Upstyle backdoor and its layers. IOC provided. 🔗 <a href="https://www.zscaler.com/blogs/security-research/look-cve-2024-3400-activity-and-upstyle-backdoor-technical-analysis" rel="nofollow noopener" translate="no" target="_blank">https://www.zscaler.com/blogs/security-research/look-cve-2024-3400-activity-and-upstyle-backdoor-technical-analysis</a><a href="https://infosec.exchange/tags/CVE_2024_3400" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_3400</a> <a href="https://infosec.exchange/tags/PaloAltoNetworks" class="mention hashtag" rel="nofollow noopener" target="_blank">#PaloAltoNetworks</a> <a href="https://infosec.exchange/tags/zeroday" class="mention hashtag" rel="nofollow noopener" target="_blank">#zeroday</a> <a href="https://infosec.exchange/tags/activeexploitation" class="mention hashtag" rel="nofollow noopener" target="_blank">#activeexploitation</a> <a href="https://infosec.exchange/tags/eitw" class="mention hashtag" rel="nofollow noopener" target="_blank">#eitw</a> <a href="https://infosec.exchange/tags/kev" class="mention hashtag" rel="nofollow noopener" target="_blank">#kev</a> <a href="https://infosec.exchange/tags/KnownExploitedVulnerabilitiesCatalog" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnownExploitedVulnerabilitiesCatalog</a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerability</a> <a href="https://infosec.exchange/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a> <a href="https://infosec.exchange/tags/threatintel" class="mention hashtag" rel="nofollow noopener" target="_blank">#threatintel</a> <a href="https://infosec.exchange/tags/IOC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IOC</a>

Not SimonCisco released 3 security advisories:<ul><li><a href="https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cimc-cmd-inj-bLuPcb" rel="nofollow noopener" target="_blank">CVE-2024-20356</a> (8.7 high) Cisco Integrated Management Controller Web-Based Management Interface Command Injection Vulnerability</li><li><a href="https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-snmp-uwBXfqww" rel="nofollow noopener" target="_blank">CVE-2024-20373</a> (5.3 medium) Cisco IOS and IOS XE Software SNMP Extended Named Access Control List Bypass Vulnerability</li><li><a href="https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cimc-cmd-inj-mUx4c5AJ" rel="nofollow noopener" target="_blank">CVE-2024-20295</a> (8.8 high) Cisco Integrated Management Controller CLI Command Injection Vulnerability</li></ul>Please note that a proof of concept was publicly disclosed for CVE-2024-20295 before it was patched, making this a zero-day. The Cisco PSIRT is not aware of any malicious use of the vulnerabilities that were described in these advisories. But don't take my word for it, go check them out yourself.<a href="https://infosec.exchange/tags/Cisco" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cisco</a> <a href="https://infosec.exchange/tags/PatchTuesday" class="mention hashtag" rel="nofollow noopener" target="_blank">#PatchTuesday</a> <a href="https://infosec.exchange/tags/zeroday" class="mention hashtag" rel="nofollow noopener" target="_blank">#zeroday</a> <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> <a href="https://infosec.exchange/tags/CVE_2024_20356" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_20356</a> <a href="https://infosec.exchange/tags/CVE_2024_20373" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_20373</a> <a href="https://infosec.exchange/tags/CVE_2024_20295" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_20295</a>

Not SimonCisco zero-day (PoC publicly disclosed): Cisco Integrated Management Controller CLI Command Injection Vulnerability CVE-2024-20295 (8.8 high) 🔗 <a href="https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cimc-cmd-inj-mUx4c5AJ" rel="nofollow noopener" translate="no" target="_blank">https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cimc-cmd-inj-mUx4c5AJ</a><blockquote>A vulnerability in the CLI of the Cisco Integrated Management Controller (IMC) could allow an authenticated, local attacker to perform command injection attacks on the underlying operating system and elevate privileges to root. To exploit this vulnerability, the attacker must have read-only or higher privileges on an affected device.This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by submitting a crafted CLI command. A successful exploit could allow the attacker to elevate privileges to root.The Cisco PSIRT is aware that proof-of-concept exploit code is available for the vulnerability that is described in this advisory.</blockquote><a href="https://infosec.exchange/tags/zeroday" class="mention hashtag" rel="nofollow noopener" target="_blank">#zeroday</a> <a href="https://infosec.exchange/tags/proofofconcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#proofofconcept</a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerability</a> <a href="https://infosec.exchange/tags/Cisco" class="mention hashtag" rel="nofollow noopener" target="_blank">#Cisco</a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerability</a> <a href="https://infosec.exchange/tags/CVE_2024_20295" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_20295</a>

Not SimonTrustedSec CTO Justin Elze shared CVE-2024-3400 exploit in the wild on Twitter yesterday, reports that <code>149.28.194.95</code> was attempting to exploit CVE-2024-3400 <a href="https://infosec.exchange/tags/CVE_2024_3400" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_3400</a> <a href="https://infosec.exchange/tags/PaloAltoNetworks" class="mention hashtag" rel="nofollow noopener" target="_blank">#PaloAltoNetworks</a> <a href="https://infosec.exchange/tags/zeroday" class="mention hashtag" rel="nofollow noopener" target="_blank">#zeroday</a> <a href="https://infosec.exchange/tags/activeexploitation" class="mention hashtag" rel="nofollow noopener" target="_blank">#activeexploitation</a> <a href="https://infosec.exchange/tags/eitw" class="mention hashtag" rel="nofollow noopener" target="_blank">#eitw</a> <a href="https://infosec.exchange/tags/kev" class="mention hashtag" rel="nofollow noopener" target="_blank">#kev</a> <a href="https://infosec.exchange/tags/KnownExploitedVulnerabilitiesCatalog" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnownExploitedVulnerabilitiesCatalog</a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerability</a> <a href="https://infosec.exchange/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a> <a href="https://infosec.exchange/tags/threatintel" class="mention hashtag" rel="nofollow noopener" target="_blank">#threatintel</a> <a href="https://infosec.exchange/tags/IOC" class="mention hashtag" rel="nofollow noopener" target="_blank">#IOC</a>

Not SimonIn case you missed it, Palo Alto Networks updated their security advisory in terms of product and mitigation guidance, exploit status, and PAN-OS fix availability: 🔗 <a href="https://security.paloaltonetworks.com/CVE-2024-3400" rel="nofollow noopener" translate="no" target="_blank">https://security.paloaltonetworks.com/CVE-2024-3400</a><ul><li>Exploitation status: Proof of concepts for this vulnerability have been publicly disclosed by third parties.</li><li>Workarounds and mitigations: In earlier versions of this advisory, disabling device telemetry was listed as a secondary mitigation action. Disabling device telemetry is no longer an effective mitigation. Device telemetry does not need to be enabled for PAN-OS firewalls to be exposed to attacks related to this vulnerability.</li><li>Solution:<ul><li>- 10.2.6-h3 (Released 4/16/24)</li><li>- 11.0.3-h10 (Released 4/16/24)</li><li>- 11.0.2-h4 (Released 4/16/24)</li><li>- 11.1.0-h3 (Released 4/16/24)</li></ul></li></ul><a href="https://infosec.exchange/tags/CVE_2024_3400" class="mention hashtag" rel="nofollow noopener" target="_blank">#CVE_2024_3400</a> <a href="https://infosec.exchange/tags/PaloAltoNetworks" class="mention hashtag" rel="nofollow noopener" target="_blank">#PaloAltoNetworks</a> <a href="https://infosec.exchange/tags/zeroday" class="mention hashtag" rel="nofollow noopener" target="_blank">#zeroday</a> <a href="https://infosec.exchange/tags/activeexploitation" class="mention hashtag" rel="nofollow noopener" target="_blank">#activeexploitation</a> <a href="https://infosec.exchange/tags/eitw" class="mention hashtag" rel="nofollow noopener" target="_blank">#eitw</a> <a href="https://infosec.exchange/tags/kev" class="mention hashtag" rel="nofollow noopener" target="_blank">#kev</a> <a href="https://infosec.exchange/tags/KnownExploitedVulnerabilitiesCatalog" class="mention hashtag" rel="nofollow noopener" target="_blank">#KnownExploitedVulnerabilitiesCatalog</a> <a href="https://infosec.exchange/tags/vulnerability" class="mention hashtag" rel="nofollow noopener" target="_blank">#vulnerability</a> <a href="https://infosec.exchange/tags/ProofofConcept" class="mention hashtag" rel="nofollow noopener" target="_blank">#ProofofConcept</a>

Recent searches

Search options

Administered by:

Server stats:

#proofofconcept