Two problems with that retort:
- It would be hard to code a patch to handle an attack vector that -- to the best of my ability to discover; and despite requests for further information and a promise of "I would release a full-disclosure document in the middle to last week of march." -- it seems has never been publicly described, let alone demonstrated.
Indeed -- whilst I'm still waiting to hear back from mitre (CVE DB maintainers) and a couple of other likely organisations -- I can find no trace that anyone other than demerphq has ever been made party to the details of the vulnerability.
- Also, based upon the scant information I have been able to glean -- and a lot of unfortunately necessary supposition -- it seems likely that any one of several one-line patches might serve to totally mitigate the possibility of CVE-2013-1667.
With the added upside that almost none of the pain caused by the implemented solution would have been necessary.
I'm preparing a paper -- which will probably come in 4 or 5 parts -- now. But it would surely be easier, and maybe even unnecessary, if disclosure were made.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|