<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Web Application on Insinuator.net - Bold Statements</title>
    <link>https://insinuator.net/tags/web-application/</link>
    <description>Recent content in Web Application on Insinuator.net - Bold Statements</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Feb 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://insinuator.net/tags/web-application/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Vulnerability Disclosure: JWT Authentication Bypass in OpenID Connect Authenticator for Tomcat</title>
      <link>https://insinuator.net/2026/02/vulnerability-disclosure-jwt-authentication-bypass-in-openid-connect-authenticator-for-tomcat/</link>
      <pubDate>Tue, 17 Feb 2026 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2026/02/vulnerability-disclosure-jwt-authentication-bypass-in-openid-connect-authenticator-for-tomcat/</guid>
      <description>&lt;p&gt;During a customer project we identified an issue with the validation of JWT&#xA;tokens that allowed us to bypass the authentication by using unsigned tokens&#xA;with arbitrary payloads. During analysis we found out that this is caused by a&#xA;vulnerability within the library&#xA;&lt;a href=&#34;https://github.com/boylesoftware/tomcat-oidcauth&#34;&gt;OpenID Connect Authenticator for Tomcat&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://github.com/boylesoftware/tomcat-oidcauth&#34;&gt;OpenID Connect Authenticator for Tomcat&lt;/a&gt;&#xA;between versions 2.0.0 and 2.5.0, as well as the current state on branch&#xA;&lt;code&gt;master&lt;/code&gt; contain a security flaw (introduced with commit &lt;code&gt;64e9a99&lt;/code&gt;) that allows&#xA;attackers to bypass JWT signature validation easily.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cookie Prefixes – The Lesser Known Cookie Security Feature</title>
      <link>https://insinuator.net/2025/04/cookie-prefixes-the-lesser-known-cookie-security-feature/</link>
      <pubDate>Tue, 08 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2025/04/cookie-prefixes-the-lesser-known-cookie-security-feature/</guid>
      <description>&lt;p&gt;When you’re analyzing web applications as a pentester or reading pentest reports&#xA;about web applications, you will often see findings regarding cookies missing&#xA;certain security flags. The &lt;em&gt;Set-Cookie&lt;/em&gt; HTTP header and the JavaScript&#xA;&lt;em&gt;document.cookie&lt;/em&gt; API allow to use, for example, the&#xA;flags &lt;em&gt;&lt;a href=&#34;https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#secure&#34;&gt;Secure&lt;/a&gt;&lt;/em&gt;, &lt;em&gt;&lt;a href=&#34;https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#pathpath-value&#34;&gt;Path&lt;/a&gt;&lt;/em&gt;, and &lt;em&gt;&lt;a href=&#34;https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Set-Cookie#domaindomain-value&#34;&gt;Domain&lt;/a&gt;&lt;/em&gt;.&#xA;Common audit and pentest tools will tell you when your web application does not&#xA;or just insecurely implements these cookie flags.&lt;/p&gt;&#xA;&lt;p&gt;However, they do not provide optimal security even when using these flags&#xA;correctly. However, there are mitigations available that partly solve the&#xA;issues.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Solving client-side controls once and for all</title>
      <link>https://insinuator.net/2022/04/solving-client-side-controls-once-and-for-all/</link>
      <pubDate>Fri, 01 Apr 2022 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2022/04/solving-client-side-controls-once-and-for-all/</guid>
      <description>&lt;p&gt;Missing server-side validation consistently scores a place in the&#xA;&lt;a href=&#34;https://owasp.org/www-project-top-ten/&#34;&gt;OWASP Top 10&lt;/a&gt;. Browsers nowadays offer&#xA;a lot of ways to easily implement client-side controls, increasing the usability&#xA;by a lot. They automatically detect missing fields or invalid characters in your&#xA;input fields and may even validate user input against a regular expressions.&lt;/p&gt;&#xA;&lt;p&gt;However, these controls should only be considered as usability features. When&#xA;sending data to a back-end system the application must always ensure data&#xA;integrity by implementing encodings, validations and filters. Even for small&#xA;applications this is a painful and tedious process. For each possible input,&#xA;developers together with security experts have to carefully identify the context&#xA;of each field, how the input is going to be used and what data requirements are&#xA;present.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Yet Another Information Disclosure?</title>
      <link>https://insinuator.net/2018/04/yet-another-information-disclosure/</link>
      <pubDate>Tue, 24 Apr 2018 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2018/04/yet-another-information-disclosure/</guid>
      <description>&lt;p&gt;Hey there, for those of you that roll your eyes when writing the nth Information Disclosure Finding in a report, here is a short story of how such information helped compromising a system.&lt;/p&gt;&#xA;&lt;p&gt;In a recent penetration we found a hidden debug page which disclosed information about internal parameters. Along with database connection strings and key material there was a username and a user home parameter disclosed on said debug page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>New Methods for Exploiting ORM Injections in Java Applications (HITB16)</title>
      <link>https://insinuator.net/2016/06/new-methods-for-exploiting-orm-injections-in-java-applications-hitb16/</link>
      <pubDate>Thu, 02 Jun 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/06/new-methods-for-exploiting-orm-injections-in-java-applications-hitb16/</guid>
      <description>&lt;p&gt;The HITBSecConf or “Hack In The Box” in Amsterdam is a well known security conference in Europe. We also attended this year too, and there were quite some interesting talks at the HITBSecConf16 conference. One of the talks was about “New Methods for Exploiting ORM Injections in Java Applications” by the security researchers Mikhail Egorov and Sergey Soldatov.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;I. What is Object-Relational Mapping (ORM)?&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;ORM stands for Object-Relational Mapping, which is a technique that automatically converts data from a relational database management system (RDBMS) into objects. This is often used in business applications of today.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Classic Web Vulns Found in Google Search Appliance 7.4</title>
      <link>https://insinuator.net/2016/03/classic-web-vulns-found-in-google-search-appliance-7.4/</link>
      <pubDate>Wed, 23 Mar 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/03/classic-web-vulns-found-in-google-search-appliance-7.4/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://www.google.com/intx/en/work/search/products/gsa.html&#34;&gt;&lt;img src=&#34;https://www.insinuator.net/wp-content/uploads/2016/03/servers-300x156.png&#34; alt=&#34;Google Search Appliances&#34;&gt;&lt;/a&gt;Hi all,&lt;/p&gt;&#xA;&lt;p&gt;I’ve recently found some sort of classic web vulnerabilities in the Google Search Appliance (GSA) and as they are now fixed [0][1][2], I’d like to share them with you.&lt;/p&gt;&#xA;&lt;p&gt;First of all, some infrastructure details about the GSA itself. The GSA is used by companies to apply the Google search algorithms to their internal documents without publishing them to cloud providers. To accomplish this task, the GSA provides multiple interfaces including a search interface, an administrative interface and multiple interfaces to index the organization’s data.&lt;/p&gt;</description>
    </item>
    <item>
      <title>How to test Kerberos authenticated web applications?</title>
      <link>https://insinuator.net/2016/02/how-to-test-kerberos-authenticated-web-applications/</link>
      <pubDate>Thu, 18 Feb 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/02/how-to-test-kerberos-authenticated-web-applications/</guid>
      <description>&lt;p&gt;First of all: This is not an in-depth Kerberos how-to, nor is this tutorial about the different aspects of web application testing. This tutorial is just to give support in testing Kerberos authenticated web applications. The goal is to hand over the right tools and steps to be able to perform the configuration and be able to test the application.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;When to use it?&lt;/strong&gt;&lt;br&gt;&#xA;When there is a 401 server response with the header “WWW-Authenticate: Negotiate”. This can either mean Kerberos or NTLM authentication is needed. It is possible to distinguish them by looking at valid authenticated client traffic. As a simple reminder: The NTLM Authorization header will always start with the value “TlRM…”, the Kerberos Authorization header will always start with “YII…”. For further information this &lt;a href=&#34;http://blogs.technet.com/b/tristank/archive/2006/08/02/negotiate-this.aspx&#34;&gt;link&lt;/a&gt; is recommend.&lt;br&gt;&#xA;In this tutorial the term “Kerberos authentication” will be used. There are other terms sometimes used like SPNEGO, SSO or integrated authentication.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Web Hacking Special Ops Workshop @ TR16</title>
      <link>https://insinuator.net/2016/01/web-hacking-special-ops-workshop-@-tr16/</link>
      <pubDate>Tue, 26 Jan 2016 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2016/01/web-hacking-special-ops-workshop-@-tr16/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Trooper!&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;You passed Hacking 1on1 with flying colors?&lt;/p&gt;&#xA;&lt;p&gt;You evade web application firewalls as they would be opened doors?&lt;/p&gt;&#xA;&lt;p&gt;You have successfully exploitated CVE-2015-8769?&lt;/p&gt;&#xA;&lt;p&gt;Then it’s time for the next challenge! Follow us down the rabbit hole to the not so well known attacks against modern web applications.&lt;/p&gt;&#xA;&lt;p&gt;At Troopers16 we will be presenting the second iteration of our WebHackingSpecialOps workshop in which more advanced techniques to break current web application technologies will be explained. On the first day there will be an introduction that gives a quick overview on the well-known attacks like SQLi, XSS and XSRF. Then attacks will be shown that build upon these “old” vectors including blind/clientside SQLi, NoSQLi and some specialties on NodeJS, the javascript based server-side runtime. Next to these technical topics several formal subjects like 3rd library handling and a guideline on how to deploy TLS in a secure way will be given. Especially the 3rd party library chapter since they have become more and more relevant, as in the near past several major vulnerabilities in such libraries were found which gave attackers the chance to break web applications that were based on these. This shows that even though developers do a great job and developer companies get familiar with secure development lifecycles, there are still problems depending on the used technologies that cannot be addressed easily. One example of such a vulnerability is the object deserialization flaw in the Apache Commons Collections library, which was discovered at the beginning of 2015 and got attention in November, when two researchers presented their &lt;a href=&#34;http://frohoff.github.io/appseccali-marshalling-pickles/&#34;&gt;talk on AppSecCali2015&lt;/a&gt; and showed how easy remote code execution can be done through this kind of flaw. The details of all kind of object deserialization (as almost all current scripting/high level programming languages support this feature) will be part of our course. Next to these topics a deep-dive into current crypto algorithms, their usecases concerning webapplications and their flaws will be given. Within every part of this course several demos and hands-on exercises will be done, so every attendee will be able to apply new knowledge directly. Don’t miss this chance to improve, Trooper!&lt;/p&gt;</description>
    </item>
    <item>
      <title>XML External Entity (XXE) Injection in Apache Batik Library [CVE-2015-0250]</title>
      <link>https://insinuator.net/2015/03/xml-external-entity-xxe-injection-in-apache-batik-library-cve-2015-0250/</link>
      <pubDate>Sat, 21 Mar 2015 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2015/03/xml-external-entity-xxe-injection-in-apache-batik-library-cve-2015-0250/</guid>
      <description>&lt;p&gt;During one of our latest web application code review projects I came across a vulnerability for which I think it is worth to speak about. It is an injection based attack against XML parsers which uses a rarely required feature called external entity expansion. The XML specification allows XML documents to define entities which reference resources external to the document and parsers typically support this feature by default. If an application parses XML input from untrusted sources and the parsing routine is not properly configured this can be exploited by an attacker with a so called XML external entity (XXE) injection. A successful XXE injection attack could allow an attacker to access the file system, cause a DoS attack or inject script code (e.g. Javascript to perform an XSS attack).&lt;/p&gt;</description>
    </item>
    <item>
      <title>ERNW’s Top 9 Burp Plugins</title>
      <link>https://insinuator.net/2014/08/ernws-top-9-burp-plugins/</link>
      <pubDate>Mon, 25 Aug 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/08/ernws-top-9-burp-plugins/</guid>
      <description>&lt;p&gt;In the context of an internal evaluation, we recently had a look at most of the burp plugins available from the BApp store. The following overview represents our personal top 9 plugins, categorized in “Scanner Extensions”, “Manual Testing” and “Misc” in alphabetic order:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Scanner Extensions&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;p&gt;ActiveScan++&lt;/p&gt;&#xA;&lt;p&gt;This plugin adds some tests for Dynamic code injection, &lt;a href=&#34;http://carlos.bueno.org/2008/06/host-header-injection.html&#34; title=&#34;Host header attacks&#34;&gt;Host header attacks&lt;/a&gt; (&lt;a href=&#34;http://www.skeletonscribe.net/2013/05/practical-http-host-header-attacks.html&#34; title=&#34;Password reset poisoning&#34;&gt;password reset poisoning&lt;/a&gt;, &lt;a href=&#34;https://www.owasp.org/index.php/Cache_Poisoning&#34; title=&#34;cache poisoning&#34;&gt;cache poisoning&lt;/a&gt;, DNS rebinding), OS command injection and &lt;a href=&#34;http://www.thespanner.co.uk/2014/03/21/rpo/&#34; title=&#34;Relative path overwrite&#34;&gt;Relative path overwrite&lt;/a&gt;. In some internal tests, it seemed to deliver what it promises.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Django Image Validation Vulnerability</title>
      <link>https://insinuator.net/2014/05/django-image-validation-vulnerability/</link>
      <pubDate>Fri, 16 May 2014 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2014/05/django-image-validation-vulnerability/</guid>
      <description>&lt;p&gt;Hi!&lt;/p&gt;&#xA;&lt;p&gt;In the course of a recent penetration test, we came across an Image validation vulnerability in Django when using the &lt;a href=&#34;http://www.pythonware.com/products/pil/&#34;&gt;Python-Imaging-Library (PIL)&lt;/a&gt; which we want to explain in this post.&lt;/p&gt;&#xA;&lt;p&gt;Everybody who doesn’t know what &lt;a href=&#34;https://www.djangoproject.com/&#34;&gt;Django&lt;/a&gt; and/or the PIL is:&lt;br&gt;&#xA;Django is a framework to create web applications with Python (comparable to Rails or Zend). The PIL is a powerful standard python library which provides a toolset to modify, display and verify images of many different formats.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Cross-Site Request Forgery with Cross-Origin Resource Sharing</title>
      <link>https://insinuator.net/2013/08/cross-site-request-forgery-with-cross-origin-resource-sharing/</link>
      <pubDate>Fri, 02 Aug 2013 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2013/08/cross-site-request-forgery-with-cross-origin-resource-sharing/</guid>
      <description>&lt;p&gt;During one of our last projects in a large environment we encountered an interesting flaw. Although it was not possible to exploit it in this particular context, it’s worth to be mentioned here. The finding was about &lt;a href=&#34;https://www.owasp.org/index.php/CSRF&#34; title=&#34;OWASP CSRF&#34;&gt;Cross-Site Request Forgery&lt;/a&gt;, a quite well-known attack that forces a user to execute unintended actions within the authenticated context of a web application. With a little help of social engineering (like sending a link via email, chat, embedded code in documents, etc…) an attacker may force the user to execute actions of the attacker’s choice.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Web Application Firewall Story continues</title>
      <link>https://insinuator.net/2012/06/the-web-application-firewall-story-continues/</link>
      <pubDate>Fri, 22 Jun 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/06/the-web-application-firewall-story-continues/</guid>
      <description>&lt;p&gt;Some days ago another &lt;a href=&#34;https://www.sec-consult.com/files/20120618-1_Airlock_WAF_overlong_UTF8_bypass.txt&#34;&gt;advisory&lt;/a&gt; related to a web application firewall (WAF) product was published. This time the product Airlock by &lt;a href=&#34;http://www.ergon.ch/&#34;&gt;Ergon&lt;/a&gt; was affected by a vulnerability that combines Encoding and NULL Byte attacks to circumvent the pattern based detection engine. We have described these attacks in detail in our newsletter “&lt;a href=&#34;http://www.ernw.de/content/e15/e28/e1659/download1661/ERNW_Newsletter_35_WAF_en_ger.pdf&#34;&gt;Web Application Firewall Security and The Swiss Army Knife for Web Application Firewalls&lt;/a&gt;” because they belong to a well known category of attacks against WAFs.&lt;/p&gt;</description>
    </item>
    <item>
      <title>SQL Injection Testing for Business Purposes Part 2</title>
      <link>https://insinuator.net/2012/05/sql-injection-testing-for-business-purposes-part-2/</link>
      <pubDate>Mon, 28 May 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/05/sql-injection-testing-for-business-purposes-part-2/</guid>
      <description>&lt;h2 id=&#34;take-care-of-the-database&#34;&gt;Take Care of the Database&lt;/h2&gt;&#xA;&lt;p&gt;There are some database specifics, every pentester should be aware of, when testing for and exploiting SQLi vulnerabilities. Besides the different string concatenation variants already covered above, there are some other specifics that have to be considered and might turn out useful in some circumstances. For example with Oracle Databases, every SELECT statement needs a following FROM statement even if the desired data is not stored within a database. So when trying to extract e.g. the DB username using a UNION SELECT statement, the DUAL table may be utilized, which should always be available. Another point, if dealing with MySQL, is the possibility to simplify the classic payload&lt;/p&gt;</description>
    </item>
    <item>
      <title>The 5 Myths of Web Application Firewalls</title>
      <link>https://insinuator.net/2012/04/the-5-myths-of-web-application-firewalls/</link>
      <pubDate>Mon, 16 Apr 2012 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2012/04/the-5-myths-of-web-application-firewalls/</guid>
      <description>&lt;p&gt;Some days ago a security advisory related to web application firewalls (WAFs) was published on Full Disclosure. Wendel Guglielmetti Henrique found another bug in the IBM Web Application Firewall which can be used to circumvent the WAF and execute typical web application attacks like SQL injection (click &lt;a href=&#34;http://lists.grok.org.uk/pipermail/full-disclosure/2011-June/081605.html&#34;&gt;here&lt;/a&gt; for details). Wendel talked already (look &lt;a href=&#34;http://troopers09.org/content/e644/e649/TROOPERS09_gauci_henrique_web_application_firewalls.pdf%20&#34;&gt;here&lt;/a&gt;) at the &lt;a href=&#34;http://www.troopers.de&#34;&gt;Troopers&lt;/a&gt; Conference in 2009 about the different techniques to identify and bypass WAFs, so this kind of bypass methods are not quite new.&lt;/p&gt;</description>
    </item>
    <item>
      <title>tsakwaf 0.9.1 released</title>
      <link>https://insinuator.net/2011/09/tsakwaf-0.9.1-released/</link>
      <pubDate>Sun, 11 Sep 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/09/tsakwaf-0.9.1-released/</guid>
      <description>&lt;p&gt;A few weeks ago, I released version 0.9 of a web application testing tool called tsakwaf (The Swiss Army Knife for Web Application Firewalls) together with an ERNW &lt;a href=&#34;http://www.ernw.de/content/e15/e28/index_ger.html&#34; title=&#34;Newsletter&#34;&gt;Newsletter&lt;/a&gt; about &lt;a href=&#34;http://www.insinuator.net/2011/06/the-5-myths-of-web-application-firewalls/&#34; title=&#34;web application firewalls&#34;&gt;web application firewalls&lt;/a&gt;. tsakwaf is based on perl and supports fingerprinting of some supported WAFs and code generation methods to circumvent filter rules. Today, version 0.9.1 will be released, which adds SSL support for the WAF fingerprinting function (Big thanks to Simon Rich!) and a bug fix regarding the detection of WAF reactions which may lead to false positives. Additionally, I’m happy to announce that at least one talk at next year’s &lt;a href=&#34;http://www.troopers.de&#34; title=&#34;Troopers&#34;&gt;Troopers&lt;/a&gt; will cover attacks against WAFs (like this one from the 2009 &lt;a href=&#34;http://troopers09.org/content/e644/e649/TROOPERS09_gauci_henrique_web_application_firewalls.pdf&#34; title=&#34;edition&#34;&gt;edition&lt;/a&gt;) . So mark your calendar – Troopers12 will happen on 21^(st) and 22^(nd) March 2012, with the usual workshops before the conference and the round table sessions the day after – and enjoy playing with tsakwaf!&lt;/p&gt;</description>
    </item>
    <item>
      <title>The 5 Myths of Web Application Firewalls</title>
      <link>https://insinuator.net/2011/06/the-5-myths-of-web-application-firewalls/</link>
      <pubDate>Mon, 27 Jun 2011 00:00:00 +0000</pubDate>
      <guid>https://insinuator.net/2011/06/the-5-myths-of-web-application-firewalls/</guid>
      <description>&lt;p&gt;Some days ago a security advisory related to web application firewalls (WAFs) was published on Full Disclosure. Wendel Guglielmetti Henrique found another bug in the IBM Web Application Firewall which can be used to circumvent the WAF and execute typical web application attacks like SQL injection (click here for details). Wendel talked already (look &lt;a href=&#34;http://troopers09.org/content/e644/e649/TROOPERS09_gauci_henrique_web_application_firewalls.pdf%20&#34;&gt;here&lt;/a&gt;) at the &lt;a href=&#34;http://www.troopers.de&#34;&gt;Troopers&lt;/a&gt; Conference in 2009 about the different techniques to identify and bypass WAFs, so this kind of bypass methods are not quite new.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
