<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Advisories on System Overlord</title><link>https://systemoverlord.com/tags/advisories.html</link><description>Recent content in Advisories on System Overlord</description><generator>Hugo</generator><language>en-us</language><managingEditor>david@systemoverlord.com (David Tomaschik)</managingEditor><webMaster>david@systemoverlord.com (David Tomaschik)</webMaster><lastBuildDate>Fri, 23 Aug 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://systemoverlord.com/tags/advisories/index.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2019-10071: Timing Attack in HMAC Verification in Apache Tapestry</title><link>https://systemoverlord.com/2019/08/23/cve-2019-10071-timing-attack-in-hmac-verification-in-apache-tapestry.html</link><pubDate>Fri, 23 Aug 2019 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2019/08/23/cve-2019-10071-timing-attack-in-hmac-verification-in-apache-tapestry.html</guid><description>&lt;h3 id="description"&gt;Description&lt;/h3&gt;
&lt;p&gt;Apache Tapestry uses HMACs to verify the integrity of objects stored on the
client side. This was added to address the Java deserialization vulnerability
disclosed in CVE-2014-1972. In the fix for the previous vulnerability, the
HMACs were compared by string comparison, which is known to be vulnerable to
timing attacks.&lt;/p&gt;
&lt;h3 id="affected-versions"&gt;Affected Versions&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Apache Tapestry 5.3.6 through current releases.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id="mitigation"&gt;Mitigation&lt;/h3&gt;
&lt;p&gt;No new release of Tapestry has occurred since the issue was reported. Affected
organizations may want to consider locally applying commit
d3928ad44714b949d247af2652c84dae3c27e1b1.&lt;/p&gt;</description></item><item><title>Playing with the Gigastone Media Streamer Plus</title><link>https://systemoverlord.com/2018/01/28/multiple-vulnerabilities-in-gigastone-media-streamer.html</link><pubDate>Sun, 28 Jan 2018 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2018/01/28/multiple-vulnerabilities-in-gigastone-media-streamer.html</guid><description>&lt;ul&gt;
&lt;li&gt;TOC
{:toc}&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="background"&gt;Background&lt;/h2&gt;
&lt;p&gt;A few months ago, I was shopping on &lt;a href="https://www.woot.com"&gt;woot.com&lt;/a&gt; and
discovered the &lt;a href="http://amzn.to/2C76sRQ"&gt;Gigastone Media Streamer Plus&lt;/a&gt; for about
$25. I figured this might be something occassionally useful, or at least fun to
look at for security vulnerabilities. When it arrived, I didn&amp;rsquo;t get around to
it for quite a while, and then when I finally did, I was terribly disappointed
in it as a security research target &amp;ndash; it was just too easy.&lt;/p&gt;</description></item><item><title>TP-Link Kasa App: SSL Verification Disabled (Fixed)</title><link>https://systemoverlord.com/2018/01/16/tp-link-kasa-app-ssl-verification-disabled-fixed.html</link><pubDate>Tue, 16 Jan 2018 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2018/01/16/tp-link-kasa-app-ssl-verification-disabled-fixed.html</guid><description>&lt;p&gt;The TP-Link Kasa app is the Android app that TP-Link distributes to control
their Smart Home line of products, including IoT light bulbs, outlet and a home
hub. TP-Link &lt;a href="http://www.tp-link.com/us/home-networking/smart-home/kasa.html"&gt;describes the app as&lt;/a&gt;:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The Kasa app works with Android and iOS devices so you can control your home
right from your smartphone or tablet. You can also use Kasa to pair TP-Link
smart home products with any Amazon Echo, Dot, Tap and The Google Assistant for
voice control, giving you the ability to control your home with voice commands.&lt;/p&gt;</description></item><item><title>[CVE-2017-17704] Broken Cryptography in iStar Ultra &amp; IP ACM by Software House</title><link>https://systemoverlord.com/2017/12/18/cve-2017-17704-broken-cryptography-in-istar-ultra-ip-acm-by-software-house.html</link><pubDate>Mon, 18 Dec 2017 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2017/12/18/cve-2017-17704-broken-cryptography-in-istar-ultra-ip-acm-by-software-house.html</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Vulnerabilities were identified in the iStar Ultra &amp;amp; IP-ACM boards offered by
Software House. This system is used to control physical access to resources
based on RFID-based badge readers. Badge readers interface with the IP-ACM
board, which uses TCP/IP to communicate with the iStar Ultra controller.&lt;/p&gt;
&lt;p&gt;These were discovered during a black box assessment and therefore the
vulnerability list should not be considered exhaustive; observations suggest
that it is likely that further vulnerabilities exist. It is strongly
recommended that Software House undertake a full whitebox security assessment of
this application. Additionally, it is our suggestion that all communications be
conducted over TLS. While alternatives are suggested below, cryptography is
very difficult even for experts, and so using a well-understood cryptosystem
like TLS is preferable to home-grown solutions. The version under test was
indicated as: 6.5.2.20569. As of the time of disclosure, the issues remain
unfixed.&lt;/p&gt;</description></item><item><title>Belden Garrettcom 6K/10K Switches: Auth Bypasses, Memory Corruption</title><link>https://systemoverlord.com/2017/05/19/belden-garrettcom-6k-10k-switches-auth-bypasses-memory-corruption.html</link><pubDate>Fri, 19 May 2017 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2017/05/19/belden-garrettcom-6k-10k-switches-auth-bypasses-memory-corruption.html</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Vulnerabilities were identified in the Belden GarrettCom 6K and 10KT (Magnum) series
network switches. These were discovered during a black box assessment and
therefore the vulnerability list should not be considered exhaustive;
observations suggest that it is likely that further vulnerabilities exist.
It is strongly recommended that GarrettCom undertake a full whitebox security
assessment of these switches.&lt;/p&gt;
&lt;p&gt;The version under test was indicated as: 4.6.0. Belden Garrettcom released
an advisory on 8 May 2017, indicating that issues were fixed in 4.7.7:
&lt;a href="https://www.belden.com/hubfs/support/security/bulletins/Belden-GarrettCom-MNS-6K-10K-Security-Bulletin-BSECV-2017-8.pdf?hsLang=en"&gt;https://www.belden.com/hubfs/support/security/bulletins/Belden-GarrettCom-MNS-6K-10K-Security-Bulletin-BSECV-2017-8.pdf?hsLang=en&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;This is a local copy of an &lt;a href="http://seclists.org/fulldisclosure/2017/May/65"&gt;advisory posted to the Full Disclosure mailing list&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Security Issues in Alerton Webtalk (Auth Bypass, RCE)</title><link>https://systemoverlord.com/2017/04/27/security-issues-in-alerton-webtalk-auth-bypass-rce.html</link><pubDate>Thu, 27 Apr 2017 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2017/04/27/security-issues-in-alerton-webtalk-auth-bypass-rce.html</guid><description>&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Vulnerabilities were identified in the Alerton Webtalk Software supplied by
Alerton. This software is used for the management of building automation
systems. These were discovered during a black box assessment and therefore
the
vulnerability list should not be considered exhaustive. Alerton has
responded
that Webtalk is EOL and past the end of its support period. Customers
should
move to newer products available from Alerton. Thanks to Alerton for prompt
replies in communicating with us about these issues.&lt;/p&gt;</description></item><item><title>ObiHai ObiPhone: Multiple Vulnerabilties</title><link>https://systemoverlord.com/2016/08/22/obihai-obiphone-multiple-vulnerabilties.html</link><pubDate>Mon, 22 Aug 2016 00:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2016/08/22/obihai-obiphone-multiple-vulnerabilties.html</guid><description>&lt;p&gt;&lt;strong&gt;Note that this a duplicate of the
&lt;a href="http://seclists.org/fulldisclosure/2016/Aug/111"&gt;advisory sent to the full-disclosure&lt;/a&gt;
mailing list.&lt;/strong&gt;&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Multiple vulnerabilities were discovered in the web management interface of the ObiHai ObiPhone products. The Vulnerabilities were discovered during a black box security assessment and therefore the vulnerability list should not be considered exhaustive.&lt;/p&gt;
&lt;h2 id="affected-devices-and-versions"&gt;Affected Devices and Versions&lt;/h2&gt;
&lt;p&gt;ObiPhone 1032/1062 with firmware less than 5-0-0-3497.&lt;/p&gt;
&lt;h2 id="vulnerability-overview"&gt;Vulnerability Overview&lt;/h2&gt;
&lt;p&gt;Obi-1. Memory corruption leading to free() of an attacker-controlled address&lt;br&gt;
Obi-2. Command injection in WiFi Config&lt;br&gt;
Obi-3. Denial of Service due to buffer overflow&lt;br&gt;
Obi-4. Buffer overflow in internal socket handler&lt;br&gt;
Obi-5. Cross-site request forgery&lt;br&gt;
Obi-6. Failure to implement RFC 2617 correctly&lt;br&gt;
Obi-7. Invalid pointer dereference due to invalid header&lt;br&gt;
Obi-8. Null pointer dereference due to malicious URL&lt;br&gt;
Obi-9. Denial of service due to invalid content-length&lt;/p&gt;</description></item><item><title>[CVE-2014-5204] Wordpress nonce Issues</title><link>https://systemoverlord.com/2014/09/10/cve-2014-5204-wordpress-nonce-issues/</link><pubDate>Wed, 10 Sep 2014 22:54:52 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2014/09/10/cve-2014-5204-wordpress-nonce-issues/</guid><description>&lt;p&gt;Wordpress 3.9.2, released August 6th, contained fixes for two closely related
vulnerabilities (CVE-2014-5204) in the way it handles Wordpress nonces (CSRF
Tokens, essentially) that I reported to the Wordpress Security Team. I&amp;rsquo;d like
to say the delay in my publishing this write-up was to allow people time to
patch, but the reality is I&amp;rsquo;ve just been busy and haven&amp;rsquo;t gotten around to this.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;TL;DR:&lt;/strong&gt; Wordpress &amp;lt; 3.9.2 generated nonces in a manner that would allow an
attacker to generate valid nonces for other users for a &lt;strong&gt;small&lt;/strong&gt; subset of
possible actions. Additionally, nonces were compared with &lt;code&gt;==&lt;/code&gt;, leading to a
timing attack against nonce comparison. (Although this is very difficult to
execute.)&lt;/p&gt;</description></item><item><title>CVE-2014-4182 &amp; CVE-2014-4183: XSS &amp; XSRF in Wordpress 'Diagnostic Tool' Plugin</title><link>https://systemoverlord.com/2014/07/04/cve-2014-4182-cve-2014-4183-xss-xsrf-in-wordpress-diagnostic-tool-plugin/</link><pubDate>Fri, 04 Jul 2014 07:00:00 +0000</pubDate><author>david@systemoverlord.com (David Tomaschik)</author><guid>https://systemoverlord.com/2014/07/04/cve-2014-4182-cve-2014-4183-xss-xsrf-in-wordpress-diagnostic-tool-plugin/</guid><description>&lt;p&gt;Versions less than 1.0.7 of the Wordpress plugin &lt;a href="https://wordpress.org/plugins/diagnostic-tool/"&gt;Diagnostic Tool&lt;/a&gt;, contain several vulnerabilities:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Persistent XSS in the Outbound Connections view. An attacker that is able to cause the site to request a URL containing an XSS payload will have this XSS stored in the database, and when an admin visits the Outbound Connections view, the payload will run. This can be trivially seen in example by running a query for &lt;code&gt;http://localhost/&amp;lt;script&amp;gt;alert(/xss/)&amp;lt;/script&amp;gt;&lt;/code&gt; on that page, then refreshing the page to see the content run, as the view is not updated in real time. This is CVE-2014-4183.&lt;/p&gt;</description></item></channel></rss>