<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:13:07 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>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CDRIVER-1691] /dev/shm/mongoc-${PID} is created in an insecure manner</title>
                <link>https://jira.mongodb.org/browse/CDRIVER-1691</link>
                <project id="10030" key="CDRIVER">C Driver</project>
                    <description>&lt;p&gt;We&apos;ve received a security report report about syslog-ng, that uses mongo-c-driver to send log messages to mongodb. The problem is actually in mongo-c-driver, and could apply to all applications using mongo-c-driver, hence this report.&lt;/p&gt;

&lt;p&gt;The shared memory block in /dev/shm/mongoc-${PID} is a predictable name, in a world writable directory without O_EXCL and O_NOFOLLOW, thus can be used to craft a symlink attack.&lt;/p&gt;

&lt;p&gt;We created this workaround that passes --disable-shm-counters to the configure script:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/balabit/syslog-ng/pull/1219&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/balabit/syslog-ng/pull/1219&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;But that won&apos;t fix distributions (once mongo-c-driver is included there) and  it would be a lot better to actually fix the problem so that mongoc-stats remains available after the fix.&lt;/p&gt;

&lt;p&gt;Is this something that you can handle with priority? Because if it is, I&apos;d not commit our workaround, but rather wait for the proper fix. If it is not, we would disable the shm based counters in our builds.&lt;/p&gt;</description>
                <environment></environment>
        <key id="322789">CDRIVER-1691</key>
            <summary>/dev/shm/mongoc-${PID} is created in an insecure manner</summary>
                <type id="1" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14703&amp;avatarType=issuetype">Bug</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="bjori">Hannes Magnusson</assignee>
                                    <reporter username="bazsi">Balazs Scheidler</reporter>
                        <labels>
                    </labels>
                <created>Tue, 11 Oct 2016 16:27:29 +0000</created>
                <updated>Mon, 26 Jun 2017 22:34:58 +0000</updated>
                            <resolved>Tue, 18 Oct 2016 22:25:32 +0000</resolved>
                                                    <fixVersion>1.5.0</fixVersion>
                                                        <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="1412101" author="xgen-internal-githook" created="Tue, 18 Oct 2016 22:20:52 +0000"  >&lt;p&gt;Author:&lt;/p&gt;
{u&apos;username&apos;: u&apos;bjori&apos;, u&apos;name&apos;: u&apos;Hannes Magnusson&apos;, u&apos;email&apos;: u&apos;bjori@php.net&apos;}
&lt;p&gt;Message: &lt;a href=&quot;https://jira.mongodb.org/browse/CDRIVER-1691&quot; title=&quot;/dev/shm/mongoc-${PID} is created in an insecure manner&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CDRIVER-1691&quot;&gt;&lt;del&gt;CDRIVER-1691&lt;/del&gt;&lt;/a&gt; /dev/shm/mongoc-${PID} is created in an insecure manner&lt;br/&gt;
Branch: master&lt;br/&gt;
&lt;a href=&quot;https://github.com/mongodb/mongo-c-driver/commit/5ef423c17126879b5618d23a4fe51f611cd7e0df&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/mongodb/mongo-c-driver/commit/5ef423c17126879b5618d23a4fe51f611cd7e0df&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="1405623" author="jesse" created="Tue, 11 Oct 2016 19:25:55 +0000"  >&lt;p&gt;&quot;it would be a lot better to actually fix the problem so that mongoc-stats remains available after the fix.&quot;&lt;/p&gt;</comment>
                            <comment id="1405523" author="bjori" created="Tue, 11 Oct 2016 18:24:03 +0000"  >&lt;p&gt;&lt;blockquote&gt;
&lt;p&gt;We created this workaround that passes --disable-shm-counters to the configure script:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://github.com/balabit/syslog-ng/pull/1219&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/balabit/syslog-ng/pull/1219&lt;/a&gt;&lt;/p&gt;&lt;/blockquote&gt; &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;</comment>
                            <comment id="1405466" author="jesse" created="Tue, 11 Oct 2016 17:37:52 +0000"  >&lt;p&gt;What&apos;s the planned workaround?&lt;/p&gt;</comment>
                            <comment id="1405406" author="bjori" created="Tue, 11 Oct 2016 16:57:23 +0000"  >&lt;p&gt;We are preparing for 1.5.0 and currently in RC phase. I imagine we can have this fix included in the next RC&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="398343">CDRIVER-2198</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hsqpxr:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>