PT SWARM – Telegram
PT SWARM
6.91K subscribers
133 photos
6 videos
1 file
198 links
Positive Technologies Offensive Team: twitter.com/ptswarm

This is the channel where we share articles/vulnerabilities/noscripts/etc, not necessarily authored by us, that we find interesting
Download Telegram
Splitting the email atom: exploiting parsers to bypass access controls

👤 by Gareth Heyes

Some websites parse email addresses to extract the domain and infer which organisation the owner belongs to. This pattern makes email-address parser discrepancies critical. Predicting which domain an email will be routed to should be simple, but is actually ludicrously difficult - even for 'valid', RFC-compliant addresses.

In this paper author is going to show you how to turn email parsing discrepancies into access control bypasses and even RCE.

This paper is accompanied by a free online CTF, so you'll be able to try out your new skill set immediately.

📝 Contents:
● Introduction
● Creating email domain confusion
● Parser discrepancies
● Punycode
● Methodology/Tooling
● Defence
● Materials
● CTF
● Takeaways
● Timeline
● References

https://portswigger.net/research/splitting-the-email-atom
👍10
Confusion Attacks: Exploiting Hidden Semantic Ambiguity in Apache HTTP Server!

👤 by Orange Tsai

This article explores architectural issues within the Apache HTTP Server, highlighting several technical debts within Httpd, including 3 types of Confusion Attacks, 9 new vulnerabilities, 20 exploitation techniques, and over 30 case studies. The content includes, but is not limited to:
🛑How a single ? can bypass Httpd’s built-in access control and authentication.
🛑How unsafe RewriteRules can escape the Web Root and access the entire filesystem.
🛑How to leverage a piece of code from 1996 to transform an XSS into RCE.


📝 Contents:
● Before the Story
● How Did the Story Begin?
● Why Apache HTTP Server Smells Bad?
● A Whole New Attack — Confusion Attack
• Filename Confusion
• DocumentRoot Confusion
• Handler Confusion
• Other Vulnerabilities
● Future Works
● Conclusion

https://blog.orange.tw/2024/08/confusion-attacks-en.html
Please open Telegram to view this post
VIEW IN TELEGRAM
👍14
World of SELECT-only PostgreSQL Injections: (Ab)using the filesystem

👤 by Maksym Vatsyk

In this article, author managed to escalate the impact of a seemingly very restricted SQL injection to a critical level by recreating DELETE and UPDATE statements from scratch via the direct modification of the DBMS files and data, and develop a novel technique of escalating user permissions!

Excessive server file read/write permissions can be a powerful tool in the wrong hands. There is still much to discover with this attack vector, but he hopes you've learned something useful today.

📝 Contents:
● Introduction
● PostgreSQL storage concepts
● Updating the PostgreSQL data without UPDATE
● SELECT-only RCE
● Conclusions
● References
● Source code

http://phrack.org/issues/71/8.html#article
👍18
This media is not supported in your browser
VIEW IN TELEGRAM
⚠️ We've confirmed critical CVE-2024-45519 in Zimbra!

SMTP-based vulnerability in postjournal service allows unauthenticated attackers to inject commands under zimbra user.

Update your software ASAP to avoid exploitation!
👍48👎1
🚀 We’re launching Positive Hack Talks! These are worldwide one-day cybersecurity meetups featuring insights from our speakers and local experts!

📍 Bengaluru, India 🇮🇳
🗓 Oct 11, 2024

Got something to share or want to join the event? Sign up today! ⬇️

https://phtalks.ptsecurity.com/
👍18
This media is not supported in your browser
VIEW IN TELEGRAM
🔥 ESET fixed CVE-2024-7400 found by our researcher Dmitriy Zuzlov!

This is an LPE that affects 13 ESET solutions and allows a low-privileged attacker to delete arbitrary files, which can be used to obtain NT AUTHORITY\SYSTEM privileges!

The advisory 👉 https://support.eset.com/en/ca8726-local-privilege-escalation-fixed-for-vulnerability-during-detected-file-removal-in-eset-products-for-windows
👍32
ATTACKING UNIX SYSTEMS VIA CUPS, PART I

👤 by Simone Margaritelli

A remote unauthenticated attacker can silently replace existing printers’ (or install new ones) IPP urls with a malicious one, resulting in arbitrary command execution (on the computer) when a print job is started (from that computer).

Entry Points
WAN / public internet: a remote attacker sends an UDP packet to port 631. No authentication whatsoever.
LAN: a local attacker can spoof zeroconf / mDNS / DNS-SD advertisements and achieve the same code path leading to RCE.

RCE chain
• Force the target machine to connect back to our malicious IPP server.
• Return an IPP attribute string that will inject controlled PPD directives to the temporary file.
• Wait for a print job to be sent to our fake printer for the PPD directives, and therefore the command, to be executed.


📝 Contents:
● Summary
● Intro
● What is cups-browsed?
● Stack Buffer Overflows and Race Conditions
● Back to found_cups_printer
● Internet Printing Protocol
● PostScript Printer Denoscription
● The problematic child: foomatic-rip
● Remote Command Execution chain
● Personal Considerations
● One More Thing


https://www.evilsocket.net/2024/09/26/Attacking-UNIX-systems-via-CUPS-Part-I/
👍22👎1
🤠 A notorious RCE in Zimbra, CVE-2024-45519 – here’s our expert breakdown!

High resolution
👍27
Ruby-SAML / GitLab Authentication Bypass (CVE-2024-45409)

👤 by Harsh Jaiswal & Rahul Maini

In this blog post, authors will analyze CVE-2024-45409, a critical vulnerability impacting Ruby-SAML, OmniAuth-SAML libraries, which effectively affects GitLab.

This vulnerability allows an attacker to bypass SAML authentication mechanisms and gain unauthorized access by exploiting a flaw in how SAML responses are handled. The issue arises due to weaknesses in the verification of the digital signature used to protect SAML assertions, allowing attackers to manipulate the SAML response and bypass critical security checks.

📝 Contents:
● Introduction
● SAML Message Verification
• How SAML Signatures Work?
• How digest and signature ensure integrity?
● Ruby-SAML Bypass
• Bypassing Signature Validation
● Conclusion

https://blog.projectdiscovery.io/ruby-saml-gitlab-auth-bypass/
👍13
🎤 Our security researcher, Konstantin Polishin, presented “Red Team Social Engineering 2024: Initial Access TTP and Project Experience of Our Team” at #ROOTCON18 🚀

Recording: https://youtube.com/watch?v=6nnZJiL0Tgk
👍29
🇻🇳 The Positive Hack Talks in Vietnam has finished!

Slides from our researcher Arseniy Sharoglazov: https://static.ptsecurity.com/events/exch-vietnam.pdf

Wordlist: https://github.com/mohemiv/dodgypass

🎁 Includes a PoC for MyQ Unauthenticated RCE! (CVE-2024-28059)
👍25
🇻🇳 At the Positive Hack Talks in Hanoi, our blue team member naumovax shared valuable insights:

1️⃣ Architecture of an automation tool for detecting malware in the network
2️⃣ Key features you should add to your tool
3️⃣ Our refined Suricata rules

Link 👉 https://static.ptsecurity.com/events/stratocaster-how-we-automated-the-routine-search-for-unknown-malware-in-the-network-traffic.pdf

Link to our Suricata rules: https://rules.ptsecurity.com/
👍24👎5
Exploiting SSTI in a Modern Spring Boot Application (3.3.4)

👤 by parzel

The article explores exploiting a Server-Side Template Injection (SSTI) vulnerability in a Spring Boot 3.3.4 application using Thymeleaf, leading to Remote Code Execution (RCE). It highlights the process of injecting malicious input to trigger Java reflection and bypass security defenses in modern framework.

The post provides a detailed walkthrough of achieving RCE despite the robust safeguards present, emphasizing the complexity of exploiting such vulnerabilities in contemporary applications.

📝 Contents:
● Identifying the Bug
● Facing Problems
● Bypassing the Defenses
● Developing the Exploit

https://modzero.com/en/blog/spring_boot_ssti/
👍32
🎮 Xbox 360 security in details: the long way to RGH3. Read the exclusive story about the chipless and reliable Xbox 360 modding method by 15432h

🔗https://swarm.ptsecurity.com/xbox-360-security-in-details-the-long-way-to-rgh3/
Please open Telegram to view this post
VIEW IN TELEGRAM
👍18
📟 Our researcher a1exdandy has uncovered vulnerabilities in GD32 microcontrollers (GigaDevice) that bypass protection mechanisms, allowing memory extraction.

The article 👉 https://swarm.ptsecurity.com/gigavulnerability-readout-protection-bypass-on-gigadevice-gd32-mcus/
👍28
🔥 The "impossible" XXE in PHP? Not so impossible anymore.

Our researcher Aleksandr Zhurnakov discovered an interesting combination of PHP wrappers and a feature of XML parsing in libxml2 to exploit it.

Read: https://swarm.ptsecurity.com/impossible-xxe-in-php/
👍54
Next.js and the corrupt middleware: the authorizing artifact

👤 by Rachid Allam & Yasser Allam

Researchers have discovered a critical vulnerability in Next.js, a popular framework for building web applications. The flaw allows attackers to bypass middleware responsible for request processing, including authentication and path rewrites.

By adding the x-middleware-subrequest header with a specific value, an attacker can completely ignore middleware execution, gaining unauthorized access to protected resources. Additionally, the vulnerability can be exploited for denial-of-service (DoS) attacks by poisoning the cache, leading to service disruption.

Many versions of Next.js are affected, making this a widespread security concern.

📝 Contents:
● The Next.js middleware
● The authorizing artifact artifact: old code, 0ld treasure
• Execution order and middlewareInfo.name
● The authorizing artifact: nostalgia has its charm, but living in the moment is better
• /src directory
• Max recursion depth
● Exploits
• Authorization/Rewrite bypass
• CSP bypass
• DoS via Cache-Poisoning (what?)
• Clarification
● Security Advisory - CVE-2025-29927
● Disclaimer
● Conclusion

https://zhero-web-sec.github.io/research-and-things/nextjs-and-the-corrupt-middleware
👍28
Don't Call That "Protected" Method: Dissecting an N-Day vBulletin RCE

👤 by Egidio Romano

The article analyzes a critical Unauthenticated Remote Code Execution vulnerability (CVE-2025-48827) in vBulletin, which becomes exploitable when running on PHP 8.1 or newer.

The vulnerability stems from vBulletin’s misuse of ReflectionMethod::invoke(), which in PHP 8.1+ no longer blocks access to protected methods by default. As a result, attackers can remotely trigger sensitive internal functions originally meant to be inaccessible and achieve code execution on the server.

📝 Contents:
● The Vulnerability
● The vBulletin Vulnerability
● Exploiting vBulletin: Path to Pre-Auth RCE
● Conclusion

https://karmainsecurity.com/dont-call-that-protected-method-vbulletin-rce
👍17