cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rhtyd <>
Subject [GitHub] cloudstack pull request #1742: CLOUDSTACK-9544: Check access on account tryi...
Date Thu, 27 Oct 2016 17:16:41 GMT
GitHub user rhtyd opened a pull request:

    CLOUDSTACK-9544: Check access on account trying to generate user API keys

    This is to merge Marc's fix on 4.8+ branches.
    Tests run:
    $ nosetests --with-xunit --xunit-file=test-results.xml --with-marvin --marvin-config=../marvin-cfgs/adv-kvm.cfg
 -s -a tags=role --zone=Sandbox-simulator --hypervisor=Simulator  test/integration/component/
    ==== Marvin Init Started ====
    === Marvin Parse Config Successful ===
    === Marvin Setting TestData Successful===
    ==== Log Folder Path: /tmp//MarvinLogs//Oct_27_2016_22_44_32_GVC833. All logs will be
available here ====
    === Marvin Init Logging Successful===
    ==== Marvin Init Successful ====
    === TestName: test_user_cannot_renew_other_keys | Status : SUCCESS ===
    === TestName: test_user_key_renew_same_account | Status : SUCCESS ===
    === TestName: test_updateAdminDetails | Status : SUCCESS ===
    === TestName: test_updateDomainAdminDetails | Status : SUCCESS ===
    === TestName: test_updateUserDetails | Status : SUCCESS ===
    ===final results are now copied to: /tmp//MarvinLogs/test_accounts_90CDC2===

You can merge this pull request into a Git repository by running:

    $ git pull cve-2016-6813

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1742
commit 158497d68a92ab1e1f864a77371ea1de5c4dc5bb
Author: Marc-Aurèle Brothier <>
Date:   2016-10-18T13:33:38Z

    CLOUDSTACK-9544: Check access on account trying to generate user API keys
    This fixes CVE-2016-6813
    Signed-off-by: Marc-Aurèle Brothier <>
    Signed-off-by: Rohit Yadav <>


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message