The remote host is affected by the vulnerability described in GLSA-201509-05 (NetworkManager: Denial of Service)

    IPv6 Neighbour Discovery ICMP broadcast containing a non-route with a       low hop limit causes a Denial of Service by lowering the hop limit on       existing IPv6 routes in NetworkManager.
  Impact :

    A remote attacker on the same network segment could cause a Denial of       Service condition in NetworkManager   Workaround :

    There is no known workaround at this time.

Updated NetworkManager packages that fix two security issues, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 7.

Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

NetworkManager is a system network service that manages network devices and connections.

It was discovered that NetworkManager would set device MTUs based on MTU values received in IPv6 RAs (Router Advertisements), without sanity checking the MTU value first. A remote attacker could exploit this flaw to create a denial of service attack, by sending a specially crafted IPv6 RA packet to disturb IPv6 communication. (CVE-2015-0272)

A flaw was found in the way NetworkManager handled router advertisements. An unprivileged user on a local network could use IPv6 Neighbor Discovery ICMP to broadcast a non-route with a low hop limit, causing machines to lower the hop limit on existing IPv6 routes. If this limit is small enough, IPv6 packets would be dropped before reaching the final destination. (CVE-2015-2924)

The network-manager-applet and NetworkManager-libreswan packages have been upgraded to upstream versions 1.0.6, and provide a number of bug fixes and enhancements over the previous versions. (BZ#1177582, BZ#1243057)

Bugs :

* It was not previously possible to set the Wi-Fi band to the 'a' or 'bg' values to lock to a specific frequency band. NetworkManager has been fixed, and it now sets the wpa_supplicant's 'freq_list' option correctly, which enables proper Wi-Fi band locking. (BZ#1254461)

* NetworkManager immediately failed activation of devices that did not have a carrier early in the boot process. The legacy network.service then reported activation failure. Now, NetworkManager has a grace period during which it waits for the carrier to appear. Devices that have a carrier down for a short time on system startup no longer cause the legacy network.service to fail. (BZ#1079353)

* NetworkManager brought down a team device if the teamd service managing it exited unexpectedly, and the team device was deactivated.
Now, NetworkManager respawns the teamd instances that disappear and is able to recover from a teamd failure avoiding disruption of the team device operation. (BZ#1145988)

* NetworkManager did not send the FQDN DHCP option even if host name was set to FQDN. Consequently, Dynamic DNS (DDNS) setups failed to update the DNS records for clients running NetworkManager. Now, NetworkManager sends the FQDN option with DHCP requests, and the DHCP server is able to create DNS records for such clients. (BZ#1212597)

* The command-line client was not validating the vlan.flags property correctly, and a spurious warning message was displayed when the nmcli tool worked with VLAN connections. The validation routine has been fixed, and the warning message no longer appears. (BZ#1244048)

* NetworkManager did not propagate a media access control (MAC) address change from a bonding interface to a VLAN interface on top of it. Consequently, a VLAN interface on top of a bond used an incorrect MAC address. Now, NetworkManager synchronizes the addresses correctly.
(BZ#1264322)

Enhancements :

* IPv6 Privacy extensions are now enabled by default. NetworkManager checks the per-network configuration files, NetworkManager.conf, and then falls back to '/proc/sys/net/ipv6/conf/default/use_tempaddr' to determine and set IPv6 privacy settings at device activation.
(BZ#1187525)

* The NetworkManager command-line tool, nmcli, now allows setting the wake-on-lan property to 0 ('none', 'disable', 'disabled').
(BZ#1260584)

* NetworkManager now provides information about metered connections.
(BZ#1200452)

* NetworkManager daemon and the connection editor now support setting the Maximum Transmission Unit (MTU) of a bond. It is now possible to change MTU of a bond interface in a GUI. (BZ#1177582, BZ#1177860)

* NetworkManager daemon and the connection editor now support setting the MTU of a team, allowing to change MTU of a teaming interface.
(BZ#1255927)

NetworkManager users are advised to upgrade to these updated packages, which correct these issues and add these enhancements.

It was discovered that NetworkManager would set device MTUs based on MTU values received in IPv6 RAs (Router Advertisements), without sanity checking the MTU value first. A remote attacker could exploit this flaw to create a denial of service attack, by sending a specially crafted IPv6 RA packet to disturb IPv6 communication. (CVE-2015-0272)

A flaw was found in the way NetworkManager handled router advertisements. An unprivileged user on a local network could use IPv6 Neighbor Discovery ICMP to broadcast a non-route with a low hop limit, causing machines to lower the hop limit on existing IPv6 routes. If this limit is small enough, IPv6 packets would be dropped before reaching the final destination. (CVE-2015-2924)

The network-manager-applet and NetworkManager-libreswan packages have been upgraded to upstream versions 1.0.6, and provide a number of bug fixes and enhancements over the previous versions.

Bugs :

  - It was not previously possible to set the Wi-Fi band to     the 'a' or 'bg' values to lock to a specific frequency     band. NetworkManager has been fixed, and it now sets the     wpa_supplicant's 'freq_list' option correctly, which     enables proper Wi-Fi band locking.

  - NetworkManager immediately failed activation of devices     that did not have a carrier early in the boot process.
    The legacy network.service then reported activation     failure. Now, NetworkManager has a grace period during     which it waits for the carrier to appear. Devices that     have a carrier down for a short time on system startup     no longer cause the legacy network.service to fail.

  - NetworkManager brought down a team device if the teamd     service managing it exited unexpectedly, and the team     device was deactivated. Now, NetworkManager respawns the     teamd instances that disappear and is able to recover     from a teamd failure avoiding disruption of the team     device operation.

  - NetworkManager did not send the FQDN DHCP option even if     host name was set to FQDN. Consequently, Dynamic DNS     (DDNS) setups failed to update the DNS records for     clients running NetworkManager. Now, NetworkManager     sends the FQDN option with DHCP requests, and the DHCP     server is able to create DNS records for such clients.

  - The command-line client was not validating the     vlan.flags property correctly, and a spurious warning     message was displayed when the nmcli tool worked with     VLAN connections. The validation routine has been fixed,     and the warning message no longer appears.

  - NetworkManager did not propagate a media access control     (MAC) address change from a bonding interface to a VLAN     interface on top of it. Consequently, a VLAN interface     on top of a bond used an incorrect MAC address. Now,     NetworkManager synchronizes the addresses correctly.

Enhancements :

  - IPv6 Privacy extensions are now enabled by default.
    NetworkManager checks the per-network configuration     files, NetworkManager.conf, and then falls back to     '/proc/sys/net/ipv6/conf/default/use_tempaddr' to     determine and set IPv6 privacy settings at device     activation.

  - The NetworkManager command-line tool, nmcli, now allows     setting the wake-on-lan property to 0 ('none',     'disable', 'disabled').

  - NetworkManager now provides information about metered     connections.

  - NetworkManager daemon and the connection editor now     support setting the Maximum Transmission Unit (MTU) of a     bond. It is now possible to change MTU of a bond     interface in a GUI.

  - NetworkManager daemon and the connection editor now     support setting the MTU of a team, allowing to change     MTU of a teaming interface.

This is an update of NetworkManager, the VPN plugins, applet and connection editor to 1.0.2 stable release.

The update includes bug fixes, feature additions, translation updates and a fix for the CVE-2015-2924 denial of service security issue with low impact.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

This update for NetworkManager fixes a number of bugs and a low-impact security issue for IPv6.

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote MiracleLinux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2015-694:01 advisory.

    ModemManager     The ModemManager service manages WWAN modems and provides a consistent API for     interacting with these devices to client applications.
    NetworkManager     NetworkManager is a system service that manages network interfaces and     connections based on user or automatic configuration. It supports     Ethernet, Bridge, Bond, VLAN, Team, InfiniBand, Wi-Fi, mobile broadband     (WWAN), PPPoE and other devices, and supports a variety of different VPN     services.
    NetworkManager-libreswan     This package contains software for integrating the libreswan VPN software     with NetworkManager and the GNOME desktop     network-manager-applet     This package contains a network control and status notification area applet     for use with NetworkManager.
    Security issues fixed with this release:
    CVE-2015-0272     GNOME NetworkManager allows remote attackers to cause a denial of     service (IPv6 traffic disruption) via a crafted MTU value in an IPv6     Router Advertisement (RA) message, a different vulnerability than     CVE-2015-8215.
    CVE-2015-2924     The receive_ra function in rdisc/nm-lndp-rdisc.c in the Neighbor     Discovery (ND) protocol implementation in the IPv6 stack in     NetworkManager 1.x allows remote attackers to reconfigure a hop-limit     setting via a small hop_limit value in a Router Advertisement (RA)     message, a similar issue to CVE-2015-2922.
    Fixed bugs:
    * It was not previously possible to set the Wi-Fi band to the a or bg values to lock to a specific     frequency band. NetworkManager has been fixed, and it now sets the wpa_supplicant's freq_list option     correctly, which enables proper Wi-Fi band locking.
    * NetworkManager immediately failed activation of devices that did not have a carrier early in the boot     process. The legacy network.service then reported activation failure. Now, NetworkManager has a grace     period during which it waits for the carrier to appear. Devices that have a carrier down for a short time     on system startup no longer cause the legacy network.service to fail.
    * NetworkManager brought down a team device if the teamd service managing it exited unexpectedly, and the     team device was deactivated. Now, NetworkManager respawns the teamd instances that disappear and is able     to recover from a teamd failure avoiding disruption of the team device operation.
    * NetworkManager did not send the FQDN DHCP option even if host name was set to FQDN. Consequently,     Dynamic DNS (DDNS) setups failed to update the DNS records for clients running NetworkManager. Now,     NetworkManager sends the FQDN option with DHCP requests, and the DHCP server is able to create DNS records     for such clients.
    * The command-line client was not validating the vlan.flags property correctly, and a spurious warning     message was displayed when the nmcli tool worked with VLAN connections. The validation routine has been     fixed, and the warning message no longer appears.
    * NetworkManager did not propagate a media access control (MAC) address change from a bonding interface to     a VLAN interface on top of it. Consequently, a VLAN interface on top of a bond used an incorrect MAC     address. Now, NetworkManager synchronizes the addresses correctly.
    Enhancements:
    * IPv6 Privacy extensions are now enabled by default. NetworkManager checks the per-network configuration     files, NetworkManager.conf, and then falls back to /proc/sys/net/ipv6/conf/default/use_tempaddr to     determine and set IPv6 privacy settings at device activation.
    * The NetworkManager command-line tool, nmcli, now allows setting the wake-on-lan property to 0 (none,     disable, disabled).
    * NetworkManager now provides information about metered connections.
    * NetworkManager daemon and the connection editor now support setting the Maximum Transmission Unit (MTU)     of a bond. It is now possible to change MTU of a bond interface in a GUI.
    * NetworkManager daemon and the connection editor now support setting the MTU of a team, allowing to     change MTU of a teaming interface.

Tenable has extracted the preceding description block directly from the MiracleLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Redhat Enterprise Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2015:2315 advisory.

    NetworkManager is a system network service that manages network devices     and connections.

    It was discovered that NetworkManager would set device MTUs based on MTU     values received in IPv6 RAs (Router Advertisements), without sanity     checking the MTU value first. A remote attacker could exploit this flaw to     create a denial of service attack, by sending a specially crafted IPv6 RA     packet to disturb IPv6 communication. (CVE-2015-0272)

    A flaw was found in the way NetworkManager handled router advertisements.
    An unprivileged user on a local network could use IPv6 Neighbor Discovery     ICMP to broadcast a non-route with a low hop limit, causing machines to     lower the hop limit on existing IPv6 routes. If this limit is small enough,     IPv6 packets would be dropped before reaching the final destination.
    (CVE-2015-2924)

    The network-manager-applet and NetworkManager-libreswan packages have been     upgraded to upstream versions 1.0.6, and provide a number of bug fixes and     enhancements over the previous versions. (BZ#1177582, BZ#1243057)

    Bugs:

    * It was not previously possible to set the Wi-Fi band to the a or bg     values to lock to a specific frequency band. NetworkManager has been fixed,     and it now sets the wpa_supplicant's freq_list option correctly, which     enables proper Wi-Fi band locking. (BZ#1254461)

    * NetworkManager immediately failed activation of devices that did not have     a carrier early in the boot process. The legacy network.service then     reported activation failure. Now, NetworkManager has a grace period during     which it waits for the carrier to appear. Devices that have a carrier down     for a short time on system startup no longer cause the legacy     network.service to fail. (BZ#1079353)

    * NetworkManager brought down a team device if the teamd service managing     it exited unexpectedly, and the team device was deactivated. Now,     NetworkManager respawns the teamd instances that disappear and is able to     recover from a teamd failure avoiding disruption of the team device     operation. (BZ#1145988)

    * NetworkManager did not send the FQDN DHCP option even if host name was     set to FQDN. Consequently, Dynamic DNS (DDNS) setups failed to update the     DNS records for clients running NetworkManager. Now, NetworkManager sends     the FQDN option with DHCP requests, and the DHCP server is able to create     DNS records for such clients. (BZ#1212597)

    * The command-line client was not validating the vlan.flags property     correctly, and a spurious warning message was displayed when the nmcli tool     worked with VLAN connections. The validation routine has been fixed, and     the warning message no longer appears. (BZ#1244048)

    * NetworkManager did not propagate a media access control (MAC) address     change from a bonding interface to a VLAN interface on top of it.
    Consequently, a VLAN interface on top of a bond used an incorrect MAC     address. Now, NetworkManager synchronizes the addresses correctly.
    (BZ#1264322)

    Enhancements:

    * IPv6 Privacy extensions are now enabled by default. NetworkManager checks     the per-network configuration files, NetworkManager.conf, and then falls     back to /proc/sys/net/ipv6/conf/default/use_tempaddr to determine and set     IPv6 privacy settings at device activation. (BZ#1187525)

    * The NetworkManager command-line tool, nmcli, now allows setting the     wake-on-lan property to 0 (none, disable, disabled). (BZ#1260584)

    * NetworkManager now provides information about metered connections.
    (BZ#1200452)

    * NetworkManager daemon and the connection editor now support setting the     Maximum Transmission Unit (MTU) of a bond. It is now possible to change MTU     of a bond interface in a GUI. (BZ#1177582, BZ#1177860)

    * NetworkManager daemon and the connection editor now support setting the     MTU of a team, allowing to change MTU of a teaming interface. (BZ#1255927)

    NetworkManager users are advised to upgrade to these updated packages,     which correct these issues and add these enhancements.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2015-2315 advisory.

    - device: reject hop limits that are too low (CVE-2015-2924) (rh #1217090)

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Published	Updated	Severity
86136	GLSA-201509-05 : NetworkManager: Denial of Service	Nessus	Gentoo Local Security Checks	9/25/2015	1/11/2021	low
87149	CentOS 7 : ModemManager / NetworkManager / NetworkManager-libreswan / network-manager-applet (CESA-2015:2315)	Nessus	CentOS Local Security Checks	12/2/2015	1/4/2021	medium
87548	Scientific Linux Security Update : NetworkManager on SL7.x x86_64 (20151119)	Nessus	Scientific Linux Local Security Checks	12/22/2015	1/14/2021	medium
83338	Fedora 22 : NetworkManager-1.0.2-1.fc22 / NetworkManager-openconnect-1.0.2-1.fc22 / etc (2015-7767)	Nessus	Fedora Local Security Checks	5/12/2015	1/11/2021	low
83504	Fedora 21 : NetworkManager-0.9.10.2-5.fc21 (2015-7623)	Nessus	Fedora Local Security Checks	5/18/2015	1/11/2021	low
289131	MiracleLinux 7 : [security - medium] NetworkManager (AXSA:2015-694:01)	Nessus	Miracle Linux Local Security Checks	1/16/2026	1/19/2026	high
86981	RHEL 7 : NetworkManager (RHSA-2015:2315)	Nessus	Red Hat Local Security Checks	11/20/2015	3/24/2025	high
87094	Oracle Linux 7 : NetworkManager (ELSA-2015-2315)	Nessus	Oracle Linux Local Security Checks	11/30/2015	11/1/2024	high

Detections

Analytics

Plugins Search

low

medium

medium

low

low

high

high

high