VaultWiki [Paid] 4.1.7 Patch Level 1
- Thread starter pegasus
- Start date
Xyphien
Active member
Made a post here: https://www.vaultwiki.org/issue.php?issueid=4645
analytic
Member
I can't buy
Warning: mysqli_query(): (42000/1064): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near ')' at line 1 in/home/vw/public_html/includes/class_core.php on line 1393
Database error
The VaultWiki - Wiki for Forum Communities database has encountered a problem.
Please try the following:
- Load the page again by clicking the Refresh button in your web browser.
- Open the www.vaultwiki.org home page, then try to open another page.
- Click the contact them if the problem persists.
We apologise for any inconvenience.
Minecraftly
Active member
I changed my main domain from m.ly to minecraftly.com, however the link to Vaultwiki is still at m.ly, causing redirect loop. Can you please help?
Minecraftly
Active member
thanks!
I´ve bought a license somehow a decade ago and never could get this addon to work in my old vb. Now I´m on XF and thought, give it a 2nd shot. Unfortunal it was a short flight by now. Followed the install instructions step by step and after importing the install.xml this happens when I click on the wiki tab to start the install script:
Guess I need your help, @pegasus .
Guess I need your help, @pegasus .
Digital Doctor
Well-known member
@Sperber - that is a super common Xenforo error.
https://xenforo.com/community/search/8266969/?q=mysqli+prepare+error&o=relevance&c[title_only]=1
https://xenforo.com/community/search/8266969/?q=mysqli+prepare+error&o=relevance&c[title_only]=1
Thanks, but Pegasus has helped me out, already. There were more things to fix as it hit the eye
triforceguy1
Active member
Do you know if this has any conflicts with XenWord, or Chat by Siropu?
pegasus
Well-known member
pegasus updated VaultWiki with a new update entry:
Changes in 4.0.11
Read the rest of this update entry...
Changes in 4.0.11
Read the rest of this update entry...
pegasus
Well-known member
pegasus updated VaultWiki with a new update entry:
Changes in 4.0.12
Read the rest of this update entry...
Changes in 4.0.12
Read the rest of this update entry...
pegasus
Well-known member
I don't have any experience with those add-ons to be able to tell you. Have you noted a problem when using both add-ons together?
Ezenity
Active member
Hey @pegasus, when I went to upgrade from version 4.0.6 to 4.0.12 build 003 I received this error
I updated my cPanel to latest release version to ensure it wasn't cPanel giving false positives. Any ideas?
Thanks
~ Mac
EDIT:
I updated my cPanel to latest release version to ensure it wasn't cPanel giving false positives. Any ideas?
Thanks
~ Mac
EDIT:
- I fixed the issue by removing this file:
- upload/vault/core/model/image/test.pdf
Last edited:
pegasus
Well-known member
From everything I have read about this, it looks like a false positive. That test.pdf is provided by Adobe and has been confirmed to be clean with other tools. I don't think Adobe would still provide that PDF if it contained a confirmed exploit.
However, if you can specify what anti-virus software gives this result, I will see if we can modify the PDF so that it passes.
EDIT: I was able to reproduce this by scanning test.pdf directly with clamscan /[path]/vault/model/image/test.pdf
Then, I downloaded the PDF, opened it, printed it as a PDF, uploaded that new PDF, and the error went away. I will update the package with the new PDF shortly.
I suspect that certain virus scanners are set to reject any PDF that was saved with certain version numbers of Acrobat appearing in the file header (test.pdf was last modified in 2006). I wonder if that might trick some versions of Acrobat Reader to use vulnerable reader versions. Unfortunately, not much information seems to be available about this vulnerability.
However, if you can specify what anti-virus software gives this result, I will see if we can modify the PDF so that it passes.
EDIT: I was able to reproduce this by scanning test.pdf directly with clamscan /[path]/vault/model/image/test.pdf
Then, I downloaded the PDF, opened it, printed it as a PDF, uploaded that new PDF, and the error went away. I will update the package with the new PDF shortly.
I suspect that certain virus scanners are set to reject any PDF that was saved with certain version numbers of Acrobat appearing in the file header (test.pdf was last modified in 2006). I wonder if that might trick some versions of Acrobat Reader to use vulnerable reader versions. Unfortunately, not much information seems to be available about this vulnerability.
Last edited:
Ezenity
Active member
I believe it's this that the exploit is finding:
http://www.symantec.com/connect/blogs/new-zero-day-pdf-exploit-used-targeted-attack
http://www.symantec.com/connect/blogs/new-zero-day-pdf-exploit-used-targeted-attack
pegasus
Well-known member
That exploit is from 2011. The one reported here is from 2016 and was patched by Adobe in May 2016. Unfortunately the virus scanner only tells us what patch Adobe gave for the vulnerability. And there were actually 93 vulnerabilities addressed by that patch:
https://helpx.adobe.com/security/products/reader/apsb16-14.html
https://helpx.adobe.com/security/products/reader/apsb16-14.html
Ezenity
Active member
Must have over looked that.
On that note, uploaded new patched version with no errors now. Thank you.
