Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 568244 (CVE-2015-8562, CVE-2015-8563, CVE-2015-8564, CVE-2015-8565) - <www-apps/joomla-3.4.8: Remote Code Execution (CVE-2015-{8562,8563,8564,8565})
Summary: <www-apps/joomla-3.4.8: Remote Code Execution (CVE-2015-{8562,8563,8564,8565})
Status: RESOLVED FIXED
Alias: CVE-2015-8562, CVE-2015-8563, CVE-2015-8564, CVE-2015-8565
Product: Gentoo Security
Classification: Unclassified
Component: Vulnerabilities (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Security
URL: https://developer.joomla.org/security...
Whiteboard: ~2 [noglsa cve]
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-14 14:58 UTC by Dainius Masiliūnas
Modified: 2016-06-30 11:39 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dainius Masiliūnas 2015-12-14 14:58:52 UTC
Joomla 3.4.6 released, with one high severity security fix and two low priority ones:

https://developer.joomla.org/security-centre/630-20151214-core-remote-code-execution-vulnerability.html
[20151214] - Core - Remote Code Execution Vulnerability
    Severity: High
    Versions: 1.5.0 through 3.4.5
    Exploit type: Remote Code Execution Vulnerability
    CVE Number: requested
Description: Browser information are not filtered properly while saving the session values into the database what leads to a Remote Code Execution vulnerability.
Affected Installs: Joomla! CMS versions 1.5.0 through 3.4.5
Solution: Upgrade to version 3.4.6

https://developer.joomla.org/security-centre/634-20151214-core-directory-traversal.html
[20151214] - Core - Directory Traversal
    Severity: Low
    Versions: 3.4.0 through 3.4.5
    Exploit type: XML File Read Issue
    CVE Number: requested
Description: Fails to properly sanitise input data from the XML install file located within the package archive.
Affected Installs: Joomla! CMS versions 3.4.0 through 3.4.5
Solution: Upgrade to version 3.4.6

https://developer.joomla.org/security-centre/633-20151214-core-csrf-hardening.html
[20151214] - Core - CSRF Hardening
    Severity: Low
    Versions: 3.2.0 through 3.4.5
    Exploit type: CSRF
    CVE Number: requested
Description: Add additional CSRF hardening in com_templates.
Affected Installs: Joomla! CMS versions 3.2.0 through 3.4.5
Solution: Upgrade to version 3.4.6
Comment 1 Harold Anderson 2016-01-03 20:42:00 UTC
You are welcome to use joomla-3.4.8 in my overlay (hnaparst)
I am the maintainer.
Comment 2 Dainius Masiliūnas 2016-01-06 18:09:42 UTC
This is now fixed by version bump in commit b278d0e2f3a50cf0e0b2b9760a3e149a8c85316b.


(In reply to Harold Naparst from comment #1)
> You are welcome to use joomla-3.4.8 in my overlay (hnaparst)

I know that, but others wouldn't, and in general having vulnerable versions of software in the main gentoo repository is not a good idea.
Comment 3 GLSAMaker/CVETool Bot gentoo-dev 2016-06-30 11:38:21 UTC
CVE-2015-8565 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8565):
  Directory traversal vulnerability in Joomla! 3.2.0 through 3.3.x and 3.4.x
  before 3.4.6 allows remote attackers to have unspecified impact via unknown
  vectors.

CVE-2015-8564 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8564):
  Directory traversal vulnerability in Joomla! 3.4.x before 3.4.6 allows
  remote attackers to have unspecified impact via directory traversal
  sequences in the XML install file in an extension package archive.

CVE-2015-8563 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8563):
  Cross-site request forgery (CSRF) vulnerability in the com_templates
  component in Joomla! 3.2.0 through 3.3.x and 3.4.x before 3.4.6 allows
  remote attackers to hijack the authentication of unspecified victims via
  unknown vectors.

CVE-2015-8562 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-8562):
  Joomla! 1.5.x, 2.x, and 3.x before 3.4.6 allow remote attackers to conduct
  PHP object injection attacks and execute arbitrary PHP code via the HTTP
  User-Agent header, as exploited in the wild in December 2015.