WishMesh http://wishmesh.com Real men don't make backups Fri, 16 Oct 2015 15:06:57 +0000 en-US hourly 1 WordPress still insecure by design http://wishmesh.com/2015/10/wordpress-still-insecure-by-design/ http://wishmesh.com/2015/10/wordpress-still-insecure-by-design/#comments Fri, 16 Oct 2015 15:06:57 +0000 http://wishmesh.com/?p=1406 Continue reading WordPress still insecure by design ]]> Some major WordPress design flaws have led to widespread attacks on our and your servers. The only hope is reasonably long and strong passwords or WordPress security plugins.

The first flaw. By default WordPress have enabled “feature”, when you visit your blog with author query string appended, it nicely reveals your usernames. For example, if you have:


just add


and default WordPress installation redirects you to the:


In you need next valid username, change 1 to 2:


The second flaw. WordPress have two separate login error messages:

ERROR: Invalid username


ERROR: The password you entered for the username admin is incorrect.

So basically, you can check if particular username is valid.

The third flaw. Many users use .htaccess to secure the wp-admin directory, but WordPress coders decided to include public accessible script in the admin folder. So securing admin folder breaks your site in many ways. Of course you can write more advanced .htaccess rules, but it is not excuse for including public script in the admin folder.

Both front-end and back-end Ajax requests use admin-ajax.php

Forth flaw. Allow hackers to iterate hundreds of usernames/passwords in the single web request (system.multicall), and do it via public accessible script, that is not hidden behind wp-admin folder. Just brilliant! By the way, flaw is still not fixed, and even if you have not so popular site, you will still see your log files full of password guessing requests from different IP addresses: - - [13/Oct/2015:17:26:55 -0400] "POST /xmlrpc.php HTTP/1.0" 200 561 "-" "-"

Note, that IP is given as an example.

Read more about this system.multicall thing here: Brute Force Amplification Attacks Against WordPress XMLRPC

The fifth flow (and not the last). If you have some flaws / vulnerabilities, please share them in comments. Of course only publicly known ones. If you have newly discovered flaw, use proper disclosure channels.

http://wishmesh.com/2015/10/wordpress-still-insecure-by-design/feed/ 0
If your source code is a trade secret, then make sure that employees and management knows that too… http://wishmesh.com/2015/09/if-your-source-code-is-a-trade-secret-then-make-sure-that-employees-and-management-knows-that-too/ http://wishmesh.com/2015/09/if-your-source-code-is-a-trade-secret-then-make-sure-that-employees-and-management-knows-that-too/#comments Fri, 18 Sep 2015 10:01:08 +0000 http://wishmesh.com/?p=1403 Continue reading If your source code is a trade secret, then make sure that employees and management knows that too… ]]> When management tries to save money, and there are no formal policies and procedures, then don’t get surprised when data leaks occur… Ungrounded Lightning shares the following story at Slashdot.

Reminds me of story about a graphics chip company

I’ll leave the company name out (mostly to protect my source B-) )

This was in the early part of the cycle of:
– A handful of companies made graphics accelerator chips..
– A BUNCH of new companies also made graphics accelerator chips.
– There was a shakeout and only a few survived – not necessarily many – or any – of the original handful.
The company in question was one of the original few.

The hardware was good. But much of the performance advantages were due to some good algorithms in the driver, which were applicable to other good, bad, or moderate capability hardware, rather than depending on special features of the company’s product.

As with many Silicon Valley companies, where the value added was so high that the administration could be utterly wacky or clueless and the company would still survive for years, this one had some managers make some dumb decisions.

One dumb decision was to try to save money by limiting the personnel to one new floppy disk per month. So the developers kept reusing the disks they had, when they shouldn’t.

As a result, the golden master for an object-only release of the driver was built on a used disk, which had once held the complete sources of the driver in question. Apparently the “reformat” process used didn’t overwrite the sectors – but the manufacturing process that cloned the golden master DID copy those sectors.

A customer tried an undelete utility and found almost the entire source code. Oops!

This news got out. Over the next couple years the great algorithms went from being a valuable trade secret (much of the company’s “secret sauce”) to a de facto industry standard.

Source: Slashdot

http://wishmesh.com/2015/09/if-your-source-code-is-a-trade-secret-then-make-sure-that-employees-and-management-knows-that-too/feed/ 0
How to save / receive jpg image or any binary data in C# Web Api 2 http://wishmesh.com/2015/08/how-to-save-receive-jpg-image-or-any-binary-data-in-c-web-api-2/ http://wishmesh.com/2015/08/how-to-save-receive-jpg-image-or-any-binary-data-in-c-web-api-2/#comments Thu, 27 Aug 2015 11:48:42 +0000 http://wishmesh.com/?p=1399 Continue reading How to save / receive jpg image or any binary data in C# Web Api 2 ]]> Searched all through the web for a simple way to save / receive binary data or image file using Web Api 2. Solutions range from very complex to complex:

  • using JSON (30% overhead?)
  • BSON (looks nice, but not widely supported – bsonspec.org)
  • Multipart MIME (why multi-part, if we have only one file?)
  • Complex Web Api / MVC controllers encapsulated by enterprise classess, etc.

They all are missing the simplest form — POST binary data, receive binary data… all in one line of code

HttpContext.Current.Request.SaveAs(filename, false);

Yes! That’s it! One line and data from Binary HTTP POST response is saved.

In case you are looking for the simple way to send binary data using the same Web Api, here is a code we are using.

HttpResponseMessage response = new HttpResponseMessage(HttpStatusCode.OK);
byte[] binaryData = File.ReadAllBytes(@"C:\full\path\to\image\photo.jpg");

if (binaryData == null) throw new FileNotFoundException("something bad happened!");
response.Content = new ByteArrayContent(binaryData);
response.Content.Headers.ContentType = new MediaTypeHeaderValue("image/jpeg");
return response;

//if your are using IHttpActionResult, use return ResponseMessage(response);

And as always, your comments are welcome! Registration is not required.

http://wishmesh.com/2015/08/how-to-save-receive-jpg-image-or-any-binary-data-in-c-web-api-2/feed/ 0