BibCiter 1.5
January 29th, 2012 by Ismael Peña-LópezPosted in Releases
Lots of stuff added since last public update, three years ago.
Hope you’ll enjoy!
Lots of stuff added since last public update, three years ago.
Hope you’ll enjoy!
As published in many places, like this one, BibCiter has been found to have multiple SQL injection vulnerabilities, due to poor treatment of variables passed through URLs (post methods) before being processed.
Here’s some “official” announcement:
BibCiter Multiple SQL Injection Vulnerabilities
SECUNIA ADVISORY ID: SA33555
VERIFY ADVISORY: http://secunia.com/advisories/33555/
CRITICAL: Moderately critical
IMPACT: Manipulation of data
WHERE: >From remote
SOFTWARE: BibCiter 1.x http://secunia.com/advisories/product/21050/
DESCRIPTION: nuclear has discovered some vulnerabilities in BibCiter, which can be exploited by malicious people to conduct SQL injection attacks.
Input passed to the “idp” parameter in reports/projects.php, to the “idc” parameter in reports/contacts.php, and to the “idu” parameter in reports/users.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code.
These vulnerabilities are confirmed in version 1.4. Other versions may also be affected.
SOLUTION: Edit the source code to ensure that input is properly sanitised.
PROVIDED AND/OR DISCOVERED BY: nuclear
ORIGINAL ADVISORY: http://milw0rm.com/exploits/7814
The solution requires time to code… time that I don’t have in the short run. So, protect yourselves at the .htaccess level.
Here’s how:
Thanks to Nassim Ettaki and David Alcubierre for valuous help :)
BibCiter v1.4 is now out.
Besides some minor issues concerning citing styles, it does fix a critical bug in the autentication process. Detected by Emilio Quintana and solved (thank you!) by Wu Jiewen, the problem was that the lenght of the password field was too short for MySQL 4.1, that needed a longer field to feed in the whole hash value. I wouldn’t have figured ever, so thanks again Jiewen!
Uh, there was a problem with a search filter that made that filter not to work properly (actually, didn’t work at all).
So we fixed it.
And improved some searching routines too.
New release - version 1.3 - comes full of new features:
Besides the existing feature to subscribe to the new works on the site, now:
rss20.xml has been deprecatedAdded the localization feature and now the site is in English and can be switched to
An incomprehensible error made it impossible for some users to install the previous version (v1.1). Incomprehensible, among other things because only retyping part of the install code, but without changing a single comma, make it work again. Weird.
Indeed. Some install features improved and added.
Some improvements too in the Projects form to better manage information.
I’ve created a plugin for WordPress so those using both applications together (WordPress and BibCiter) can easily cite in the former content at the later.
The plugin can add from one to three WordPress shortcodes so that embedding BibCiter citations in blog posts do not require but knowing the ID of a Work or an Author. The shortcodes are the following:
To properly work, both BibCiter and WordPress must be installed under the same domain - though with simplest coding this can be easily changed.
Here comes v1.1. The main change has been some little adaptations to be able to support a WordPress plugin and some issues about shifting towards charset UTF-8. I’m sorry about the latter because no doubt it will cause problems with some characters (especially for those using BibCiter with languages full of “special” characters). There’s some stuff on the Internet that can help in the transition. Patience will also play a good part.
Improvements in this v1.1 release:
I’m really proud to announce that, at last, v1.0 of BibCiter will see the light.
After two years and a half coding (!!!) and intensive use, I guess the creature is ready to have a life as a decent 1.0, no 0.anything, no betas.
This does not mean there is nothing to be improved, but let’s leave these improvements for v1.x or v2.0.
Improvements in this v1.0 release:
By the way, I dediced to remove the addition of sample data in the installation process, because I thought it just added noise and, sometimes, was a source of problems. I don’t think anybody’s gonna miss this ;)
This is a pretty good update with pretty improved features.