Application Security This Week for September 30

The "Wow, it's been a busy month" edition.


Apple took "Adware Doctor" out of the store because it was stealing data.  How did no one notice this?


There is a new search engine for researching exploits.


Google open sourced their file upload protection tool.


A cheat sheet for Angular web security.


SharpSploit: a C# post-exploitation library.



Application Security This Week for September 9

MWR Labs describes use of HTTP Referer headers to execute DNS rebinding attacks on AWS-hosted analytics systems


Malicious PowerShell Compiling C# Code on the Fly


Interesting bug in Chromium


Holy crap there are a lot of Cisco security patches this month.

Application Security This Week for September 2

Mazen Ahmed write an exploit for the new Struts CVE.


Speaking of the CVE program, and MITRE in general, Steve Ragan got a solid scoop on congress planning a revamp.


Secure Ideas started a blog seried on CORS, CSRF, and Clickjacking which is off to a good start


The Fortnite Android app is vulnerable to a really very unique flaw, Man-on-the-disk.


Speaking of weird flaws, people have started registering skills on Alexa with phonetically similar names as common commands. It's called Skill Squatting.


And that's the news!

Application Security This Week for August 26

Big, big news out of Portswigger this week.  I'm a huge fan of OWASP ZAP, and use it daily, but this is a major uptick in web analysis tools.

A new API for Burp Suite (something ZAP has had for years)

The introduction of 2.0

And finally the introduction of Enterprise Edition, which effectively adds scalibility

Really solid week of announcements.


In other news, AppSec consulting hits it out of the park again with advice on securing third-party JavaScript.


A major flaw was found in GhostScript.  If you are parsing document formats like PDF or XPS, get your patch on!


Another Struts RCE vulnerability.  "I'm shocked!" said nobody, ever.


Bitdefender published a whitepaper on the next phase of Android malware, and it is worth a read.


And that's the news!

Application Security this Week for August 19

Trend Micro found a really interesting use-after-free vulnerability in the VBScript engine in IE.  Now, before you giggle, think of all of the companies that have standardized on IE. They are out there. Either way, the finding is cool.


Username enumeration bug discovered in OpenSSH of all things.


Ever seen a scanner point out that a site is vulnerable to DNS Rebinding, and wonder what the heck it was talking about?  Yeah me too.  These folks wrote up a framework for it.


Here is a password list sorted by probability. Remember that training course when I said you should check your new passwords against a list of known bad values, because NIST said to? Here ya go. The esteemed Jim Fenton recommends checking against the first 100,000. Neat project.

Application Security This Week for August 12

Interesting idea - introducing bugs to make software more difficult to attackers to navigate.  Seems risky to me; I would rather see self-reporting software.


Cloudflare has a really really good writeup on TLS 1.3.


Questionably ethical hacker steals credentials from the Homebrew repo and makes a commit.


Viral tweet thread on the "voatz" software that WVa is planning on using for midterm elections. Vulnerabilityapalooza.


Portswigger posted a nice primer on cache poisoning.

Application Security Weekly for August 5

Reddit Breach Highlights Limits of SMS-Based Authentication


One of my favorite people - Adam Caudill with AppSec Consulting - gives a breakdown of changes to the way Chrome handles HTTPS


Information disclosure is a thing - stop using Trello as a password manager


One of my favorite companies (Duo) has been acquired by Cisco

I have been assured that everything is gonna be OK 


As nosqlmap has fallen a bit by the wayside, I'm glad to see a new NoSQL scanner show up

Application Security This Week for July 29

Venmo, a social payment system, defaults to public disclosure of payments made on the system.


Scott Simmons has some terriffic advice about using Same-Origin policy as a control for CSRF.


Open redirect flaw in Electron exploites in the new Google Hangouts Chat application.


F5 has released their annual Application Protection report.  Worth a read.


DOMpurify, a common control for DOM based XSS, has a vulnerability - update if you are using it (you probably are).

Application Security This Week for July 22

It has come to my attention that one of Paul Asadoorian's Security Weekly broadcasts is titled Application Security Weekly! I had no idea. It's good too, you should listen.  I caught up with the last few weeks when I drove over to Indianapolis to chat with the Indy Software Artisans meetup.  Anyway, I am changing the title of this recurring series of posts to Application Security This Week because of the mixup.


Interesting discussion over at El Reg about the weakest link in software security.


Oracle addressed 334 security vulnerabilities in its latest patch series.


Shape Security did the math, and 9 out of 10 login attempts on the web are bypass attempts.

Raspberry Pi project: network speed tester

For my home internet, I have one choice - Spectrum, née Time Warner Cable.  I don't completely live in the boonies but it is far enough away from everything that I can't get anything but cable, and Time Warner is the only cable company I got.  Honestly it hasn't been bad - I have been a customer since they were Roadrunner, and have had nearly zero problems.  Had a mixup when we moved our phone service to them, which led to us dropping phone altogether and just using mobile (and the alarm system for emergencies). Had a couple useless repair folks.  Over a 20 year history with them, I'm pretty pleased.

However, we have started having brownouts.  We'll be tooting along, then the feed will go to a dribble. I pay for 50 Mbps down, and usually get 70, but then it will be 500 Kbps for hours.  Then it will be fine.  Is it Spectrum?  My modem?  My router?  Something else on my network? I wasn't sure, so I would lug my laptop back there, plug the ethernet from the cable model directly in, and run Speedtest. Started to get some data.  Then, the laptop that had an ethernet port went titsup.  Now what?

Enter the Speedtest Pi.  I scrapped a screen from an old POS appliance that I tested and was allowed to keep, an old mini keyboard, and one of the dozen Pis that I have laying around from various programs I have taught, and built a semi-permanent speed test appliance that I can go and use anytime I want.

I did need to buy an AV shield at Microcenter so I didn't have to soldier the heck out of the Pi, but that's OK. This was a quick and dirty job, and the shield was only $15.

Now - best way to do the speedtest?  Well, did you know there is a Speedtest API? I DID NOT.  To make it even better, there is a speedtest command line interface app in the install paths for Raspbian.  So I simply:

sudo apt-get install speedtest-cli

and that's all there was to it.

Next next step is to put a fast switch in, so that I can leave it on all the time, and then have it run every hour or so, and show a graph on the screen.  Should be a fun Python project.

Husband. Father. Pentester. Secure software composer. Brewer. Lockpicker. Ninja. Insurrectionist. Lumberjack. All words that have been used to describe me recently. I help people write more secure software.



profile for Bill Sempf on Stack Exchange, a network of free, community-driven Q&A sites