logo
Apache Lounge
Webmasters

 


About

Forum Index Downloads Search Register Log in  RSS Apache Lounge
 



Keep Server Online

If you find the Apache Lounge, the downloads and overall help useful, please express your satisfaction with a donation.

or

Bitcoin

A donation makes a contribution towards the costs, the time and effort that's going in this site and building.

Thank You! Steffen

Apache Lounge is not sponsored.

Your donations will help to keep this site alive and well, and continuing building binaries.



EU's final report on audit of Apache HTTP and APR is out.

 
Post new topic   Reply to topic    Apache Forum Index -> News & Hangout



View previous topic :: View next topic  
Author Message
glsmith
Moderator


Joined: 16 Oct 2007
Posts: 2123
Location: Sun Diego, USA

PostPosted: Thu 17 Nov '16 2:10    Post subject: EU's final report on audit of Apache HTTP and APR is out. Reply with quote

https://joinup.ec.europa.eu/sites/default/files/ckeditor_files/files/DLV%20WP6%20-01-%20ApacheCoreAPR%20Code%20Review_published.pdf

2 issues considered low
5 informational

4 of these do not have a impact on the actual server or libraries because they are only used during the compilation of the code and are not part of the distributions to end users so may be change in accordance to the recommendations if someone gets an itch to do it.

1 is unix specific.

I do see two that will be (just saw a patch for CBC-FIO-001 come in the mail)
or may have already been fixed in the source (I haven't checked).

The last two paragraphs of the report are quite telling as to the security posture of APR/HTTP.
Quote:
In conclusion , the code review carried out confirmed the fact that the code of both Apache Core and APR have a good level from a security point of view, with only a few controls with findings, none of them being of high severity.

As a final note , it is fundamental to take into account that these findings cannot be directly considered security flaws that can be exploited, since ‘Security’ is a set of layers and therefore several risky findings are necessary to compromise the software.

Another thing to note, they do add this caveat often;
Quote:
Before deciding to change it, one must take into account the risk of adding more complexity to the code.
Back to top


Post new topic   Reply to topic    Apache Forum Index -> News & Hangout
Page 1 of 1