<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:08:46 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[AAA-151] Previous password continues to work after password change</title>
                <link>https://jira.opendaylight.org/browse/AAA-151</link>
                <project id="10102" key="AAA">aaa</project>
                    <description>&lt;p&gt;#security-status: confirmed-leaked&lt;/p&gt;

&lt;p&gt; This issue has been confirmed as a security vulnerability in&lt;br/&gt;
 OpenDayLight AAA. Unfortunately the details of this flaw have been&lt;br/&gt;
 made public. Therefore it cannot be fixed under the OpenDaylight &lt;br/&gt;
embargoed security vulnerability process. As this issue is now public &lt;br/&gt;
it is important that the flaw is addressed in a timely manner. The &lt;br/&gt;
OpenDaylight security team will ensure that a CVE is assigned for this issue.&lt;/p&gt;

&lt;p&gt;Vaibhav Hemant Dixit reported the following security vulnerability to the security mailing list:&lt;/p&gt;

&lt;p&gt;Severity : OPENDAYLIGHT AUTHENTICATION BREACHED&lt;/p&gt;

&lt;p&gt;Issue: After updating the password, the login is successful with both OLD and NEW passwords&lt;br/&gt;
Controller: Distribution Version: distribution-karaf-0.6.1-Carbon.tar.gz&lt;/p&gt;

&lt;p&gt;Steps to reproduce:&lt;/p&gt;

&lt;p&gt;    Start the controller.&lt;br/&gt;
    Install feature on Karaf: &quot;feature:install odl-aaa-cli &quot;&lt;br/&gt;
    Changed the admin password :&lt;br/&gt;
    _aaa:change-user-pwd -user admin&lt;br/&gt;
    Enter current password:&lt;br/&gt;
    Enter new password:&lt;br/&gt;
    admin&apos;s password has been changed_&lt;/p&gt;

&lt;p&gt;Observation:&lt;/p&gt;

&lt;p&gt;    The admin user can authenticate using both OLD and NEW passwords.&lt;br/&gt;
    Execute a REST call with OLD and new password, the authentication is successful.&lt;br/&gt;
    If the controller is shutdown and restarted, the issue is not seen anymore.&lt;/p&gt;</description>
                <environment></environment>
        <key id="28873">AAA-151</key>
            <summary>Previous password continues to work after password change</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</priority>
                        <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="rgoulding">Ryan Goulding</assignee>
                                    <reporter username="vhd">Vaibhav Hemant Dixit</reporter>
                        <labels>
                    </labels>
                <created>Tue, 21 Nov 2017 16:53:15 +0000</created>
                <updated>Tue, 28 Nov 2017 18:22:01 +0000</updated>
                            <resolved>Tue, 28 Nov 2017 18:22:01 +0000</resolved>
                                                    <fixVersion>Carbon-SR3</fixVersion>
                    <fixVersion>Nitrogen-SR1</fixVersion>
                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="60120" author="rgoulding" created="Tue, 21 Nov 2017 19:05:32 +0000"  >&lt;p&gt;Proposed fix:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/q/topic:AAA-151&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/q/topic:AAA-151&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Affects CLI only;  the REST endpoints do Claim cache invalidation already.  Reboot works because the ClaimCache is force-flushed upon exit of the Java process.  Although the CLI requires system access for (bin/client) or SSH access to the Karaf process, the effects are still bad because an admin expects that the old password should not work after he/she has changed it.  He or she invokes the change-user-password Karaf CLI command expecting that the old credentials will no longer be accepted.&lt;/p&gt;

&lt;p&gt;Not sure how we want to handle this, but I&apos;d imagine it involves CVE and proper documentation.  The fixes will be merged to the affected branches (carbon, nitrogen &amp;amp; master) as they pass jenkins-releng.&lt;/p&gt;</comment>
                            <comment id="60123" author="lukehinds" created="Wed, 22 Nov 2017 09:42:12 +0000"  >&lt;p&gt;&lt;del&gt;Recommended Disclosure Dates&lt;/del&gt;&lt;/p&gt;

&lt;p&gt;&lt;del&gt;Thursday 23/11 - Downstream Stakeholders&lt;/del&gt;&lt;/p&gt;

&lt;p&gt;&lt;del&gt;Wednesday 29/11 - Go Public, open this JIRA and notify public mailing addresses.&lt;/del&gt;&lt;/p&gt;</comment>
                            <comment id="60124" author="lukehinds" created="Wed, 22 Nov 2017 10:01:56 +0000"  >&lt;p&gt;&lt;a href=&quot;https://jira.opendaylight.org/secure/ViewProfile.jspa?name=rgoulding&quot; class=&quot;user-hover&quot; rel=&quot;rgoulding&quot;&gt;rgoulding&lt;/a&gt; et al, please verify the impact description:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Title: Previous passwords remain active after a password change, when using the Karaf CLI.&lt;/p&gt;

&lt;p&gt;Reporters:     &lt;br/&gt;
Vaibhav Hemant Dixit, Arizona State University &lt;/p&gt;

&lt;p&gt;Affects: OpenDayLight AAA&lt;br/&gt;
Versions: Carbon, Nitrogen&lt;/p&gt;

&lt;p&gt;Risk-assessment:&lt;br/&gt;
impact-rating: Important&lt;/p&gt;

&lt;p&gt;Description:&lt;/p&gt;

&lt;p&gt;Vaibhav Hemant Dixit from Arizona State University reported a vulnerability&lt;br/&gt;
in OpenDayLight AAA, whereby should a user update a password, the login is still successful with both OLD and NEW passwords. This is a result of how claimCache is flushed in AAA IDM when using the Karaf CLI. The issue is not present when using the AAA IDM REST API, as the handlers already invoke the clearing of the IdmLightProxy claimCache upon user update. A flush can be made by performing a reboot of Karaf or by applying the patches referenced in this advisory, as the patches enable the Karaf CLI to call IdmLightProxy claimCache and perform a flush every time a user changes a password.&lt;/p&gt;

&lt;p&gt;Versions Affected: Nitrogen &amp;amp; Carbon&lt;/p&gt;&lt;/blockquote&gt;</comment>
                            <comment id="60257" author="rgoulding" created="Tue, 28 Nov 2017 17:20:38 +0000"  >&lt;p&gt;My apologies, I was out for the Holiday weekend.&#160; This seems accurate to me.&#160; Thanks for your help with this issue.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10001">
                    <name>Cloners</name>
                                                                <inwardlinks description="is cloned by">
                                                        </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i038cf:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>