<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>NRF Connect SDK / NRFXLIB security vulnerabilities</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/120834/nrf-connect-sdk-nrfxlib-security-vulnerabilities</link><description>I am currently in the process of filling out the 18031 RED Cybersecurity certification documentation. I am currently analyzing the security vulnerabilities list of NCS v1.4.2 (link below) and noticed that its only referencing vulnerabilities for the zephyr</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 28 Apr 2025 20:06:05 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/120834/nrf-connect-sdk-nrfxlib-security-vulnerabilities" /><item><title>RE: NRF Connect SDK / NRFXLIB security vulnerabilities</title><link>https://devzone.nordicsemi.com/thread/533266?ContentTypeID=1</link><pubDate>Mon, 28 Apr 2025 20:06:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:50ceee7c-dfb2-4cff-828f-9fc3c038c911</guid><dc:creator>Jameson</dc:creator><description>&lt;p&gt;Thanks for the info!&amp;nbsp; Yea I think that answers things, I&amp;#39;ll wait to&amp;nbsp;hear when those public vulnerabilities are provided.&amp;nbsp; Until then I&amp;#39;m just going to rely on the NVD database for things.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
[quote userid="77062" url="~/f/nordic-q-a/120834/nrf-connect-sdk-nrfxlib-security-vulnerabilities/533260"]Are you using MCUboot?[/quote]
&lt;p&gt;No we are not using MCUboot.&amp;nbsp; We&amp;nbsp;were very early integrators of the NRF9160 and for security reasons ended up making our own bootloader.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF Connect SDK / NRFXLIB security vulnerabilities</title><link>https://devzone.nordicsemi.com/thread/533260?ContentTypeID=1</link><pubDate>Mon, 28 Apr 2025 19:12:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9025b95e-5674-4b9c-865e-91c4688a1eec</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello again, and my apologies for the late reply.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;From what I&amp;#39;m informed we are in a process of publishing a&amp;nbsp;&lt;span&gt;public vulnerability list on our website but unfortunately this is still work in progress.&amp;nbsp; For mbed-TLS the list of vulnerability should be&amp;nbsp;compared to the &lt;a href="https://github.com/Mbed-TLS/mbedtls"&gt;mbed-TLS public git repo&lt;/a&gt;. NCS 1.4.2 integrates v2.23.0 of mbed-TLS. However, Zephyr may also be using this version. Are you using MCUboot?&lt;/span&gt;&lt;/p&gt;
[quote user="Jameson Bickert Appareo"]4. I looked up the specific zephyr product/version in the NVD that I&amp;#39;m using ncs 1.4.2 and zephyr 2.4.0 (its a bit behind).&amp;nbsp; Would this be the correct list to reference for current vulnerabilities for the zephyr repo used within the nrf connect sdk?&amp;nbsp; &amp;nbsp;[/quote]
&lt;p&gt;This seems to be an accurate list. Zephyr doesn&amp;#39;t backport fixes to all previous versions, but unfortunately and in most cases when a vulnerability is found it affects all previous versions (or at least until the point the new piece of code was added). As the Zephyr version you are using is quite old, there is no surprise that it has some vulnerabilities&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF Connect SDK / NRFXLIB security vulnerabilities</title><link>https://devzone.nordicsemi.com/thread/532422?ContentTypeID=1</link><pubDate>Tue, 22 Apr 2025 16:34:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5ca12e8-0382-4577-9656-fa012b10f85a</guid><dc:creator>Jameson</dc:creator><description>&lt;p&gt;Thanks&amp;nbsp;&lt;span&gt;&amp;Oslash;yvind!&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;I have some additional questions as well based on me digging in more.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;3. I think I misunderstood the `vulnerabilities.html` document as being the active vulnerabilities for the zephyr product.&amp;nbsp; After reading the top it seems like its the vulnerabilities RESOLVED for the current release.&amp;nbsp; Can you confirm?&lt;/p&gt;
&lt;p&gt;4. I looked up the specific zephyr product/version in the NVD that I&amp;#39;m using ncs 1.4.2 and zephyr 2.4.0 (its a bit behind).&amp;nbsp; Would this be the correct list to reference for current vulnerabilities for the zephyr repo used within the nrf connect sdk?&amp;nbsp; &amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://nvd.nist.gov/vuln/search/results?adv_search=true&amp;amp;isCpeNameSearch=true&amp;amp;query=cpe%3A2.3%3Ao%3Azephyrproject%3Azephyr%3A2.4.0%3A-%3A*%3A*%3A*%3A*%3A*%3A*"&gt;https://nvd.nist.gov/vuln/search/results?adv_search=true&amp;amp;isCpeNameSearch=true&amp;amp;query=cpe%3A2.3%3Ao%3Azephyrproject%3Azephyr%3A2.4.0%3A-%3A*%3A*%3A*%3A*%3A*%3A*&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF Connect SDK / NRFXLIB security vulnerabilities</title><link>https://devzone.nordicsemi.com/thread/532367?ContentTypeID=1</link><pubDate>Tue, 22 Apr 2025 13:14:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2ab7dce3-1661-4923-b8f4-d65e9e8e8f70</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello, I&amp;#39;ve been assigned you ticket and currently investigating internally.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;I hope to get back to you within Thursday or Friday this week.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>