CVE-2015-9236 Vulnerability Analysis & Exploit Details

CVE-2015-9236 Vulnerability Summary

CVE-2015-9236: Hapi versions less than 11.0.0 implement CORS incorrectly and allowed for configurations that at best returned inconsistent headers and at worst allowed cross-origin activities that were expected to be forbidden. If the connection has CORS enabled but one route has it off, and the route is not GET, the OPTIONS prefetch request will return the default CORS headers and then the actual request will go through and return no CORS headers. This defeats the purpose of turning CORS on the route.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.112% (probability of exploit)

EPSS Percentile: 46.34% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 53.66% of others.

CVE-2015-9236 References

External References

• https://github.com/hapijs/hapi/issues/2840
• https://github.com/hapijs/hapi/issues/2850
• https://nodesecurity.io/advisories/45
• https://github.com/hapijs/hapi/issues/2840
• https://github.com/hapijs/hapi/issues/2850
• https://nodesecurity.io/advisories/45

CWE Common Weakness Enumeration

CAPEC Common Attack Pattern Enumeration and Classification

• Excavation CAPEC-116 An adversary actively probes the target in a manner that is designed to solicit information that could be leveraged for malicious purposes.
• Subverting Environment Variable Values CAPEC-13 The adversary directly or indirectly modifies environment variables used by or controlling the target software. The adversary's goal is to cause the target software to deviate from its expected operation in a manner that benefits the adversary.
• Footprinting CAPEC-169 An adversary engages in probing and exploration activities to identify constituents and properties of the target.
• Exploiting Trust in Client CAPEC-22 An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
• Fingerprinting CAPEC-224 An adversary compares output from a target system to known indicators that uniquely identify specific details about the target. Most commonly, fingerprinting is done to determine operating system and application versions. Fingerprinting can be done passively as well as actively. Fingerprinting by itself is not usually detrimental to the target. However, the information gathered through fingerprinting often enables an adversary to discover existing weaknesses in the target.
• ICMP Echo Request Ping CAPEC-285 An adversary sends out an ICMP Type 8 Echo Request, commonly known as a 'Ping', in order to determine if a target system is responsive. If the request is not blocked by a firewall or ACL, the target host will respond with an ICMP Type 0 Echo Reply datagram. This type of exchange is usually referred to as a 'Ping' due to the Ping utility present in almost all operating systems. Ping, as commonly implemented, allows a user to test for alive hosts, measure round-trip time, and measure the percentage of packet loss.
• TCP SYN Scan CAPEC-287 An adversary uses a SYN scan to determine the status of ports on the remote target. SYN scanning is the most common type of port scanning that is used because of its many advantages and few drawbacks. As a result, novice attackers tend to overly rely on the SYN scan while performing system reconnaissance. As a scanning method, the primary advantages of SYN scanning are its universality and speed.
• Enumerate Mail Exchange (MX) Records CAPEC-290 An adversary enumerates the MX records for a given via a DNS query. This type of information gathering returns the names of mail servers on the network. Mail servers are often not exposed to the Internet but are located within the DMZ of a network protected by a firewall. A side effect of this configuration is that enumerating the MX records for an organization my reveal the IP address of the firewall or possibly other internal systems. Attackers often resort to MX record enumeration when a DNS Zone Transfer is not possible.
• DNS Zone Transfers CAPEC-291 An attacker exploits a DNS misconfiguration that permits a ZONE transfer. Some external DNS servers will return a list of IP address and valid hostnames. Under certain conditions, it may even be possible to obtain Zone data about the organization's internal network. When successful the attacker learns valuable information about the topology of the target organization, including information about particular servers, their role within the IT structure, and possibly information about the operating systems running upon the network. This is configuration dependent behavior so it may also be required to search out multiple DNS servers while attempting to find one with ZONE transfers allowed.
• Host Discovery CAPEC-292 An adversary sends a probe to an IP address to determine if the host is alive. Host discovery is one of the earliest phases of network reconnaissance. The adversary usually starts with a range of IP addresses belonging to a target network and uses various methods to determine if a host is present at that IP address. Host discovery is usually referred to as 'Ping' scanning using a sonar analogy. The goal is to send a packet through to the IP address and solicit a response from the host. As such, a 'ping' can be virtually any crafted packet whatsoever, provided the adversary can identify a functional host based on its response. An attack of this nature is usually carried out with a 'ping sweep,' where a particular kind of ping is sent to a range of IP addresses.
• Traceroute Route Enumeration CAPEC-293 An adversary uses a traceroute utility to map out the route which data flows through the network in route to a target destination. Tracerouting can allow the adversary to construct a working topology of systems and routers by listing the systems through which data passes through on their way to the targeted machine. This attack can return varied results depending upon the type of traceroute that is performed. Traceroute works by sending packets to a target while incrementing the Time-to-Live field in the packet header. As the packet traverses each hop along its way to the destination, its TTL expires generating an ICMP diagnostic message that identifies where the packet expired. Traditional techniques for tracerouting involved the use of ICMP and UDP, but as more firewalls began to filter ingress ICMP, methods of traceroute using TCP were developed.
• ICMP Address Mask Request CAPEC-294 An adversary sends an ICMP Type 17 Address Mask Request to gather information about a target's networking configuration. ICMP Address Mask Requests are defined by RFC-950, "Internet Standard Subnetting Procedure." An Address Mask Request is an ICMP type 17 message that triggers a remote system to respond with a list of its related subnets, as well as its default gateway and broadcast address via an ICMP type 18 Address Mask Reply datagram. Gathering this type of information helps the adversary plan router-based attacks as well as denial-of-service attacks against the broadcast address.
• Timestamp Request CAPEC-295 This pattern of attack leverages standard requests to learn the exact time associated with a target system. An adversary may be able to use the timestamp returned from the target to attack time-based security algorithms, such as random number generators, or time-based authentication mechanisms.
• ICMP Information Request CAPEC-296 An adversary sends an ICMP Information Request to a host to determine if it will respond to this deprecated mechanism. ICMP Information Requests are a deprecated message type. Information Requests were originally used for diskless machines to automatically obtain their network configuration, but this message type has been superseded by more robust protocol implementations like DHCP.
• TCP ACK Ping CAPEC-297 An adversary sends a TCP segment with the ACK flag set to a remote host for the purpose of determining if the host is alive. This is one of several TCP 'ping' types. The RFC 793 expected behavior for a service is to respond with a RST 'reset' packet to any unsolicited ACK segment that is not part of an existing connection. So by sending an ACK segment to a port, the adversary can identify that the host is alive by looking for a RST packet. Typically, a remote server will respond with a RST regardless of whether a port is open or closed. In this way, TCP ACK pings cannot discover the state of a remote port because the behavior is the same in either case. The firewall will look up the ACK packet in its state-table and discard the segment because it does not correspond to any active connection. A TCP ACK Ping can be used to discover if a host is alive via RST response packets sent from the host.
• UDP Ping CAPEC-298 An adversary sends a UDP datagram to the remote host to determine if the host is alive. If a UDP datagram is sent to an open UDP port there is very often no response, so a typical strategy for using a UDP ping is to send the datagram to a random high port on the target. The goal is to solicit an 'ICMP port unreachable' message from the target, indicating that the host is alive. UDP pings are useful because some firewalls are not configured to block UDP datagrams sent to strange or typically unused ports, like ports in the 65K range. Additionally, while some firewalls may filter incoming ICMP, weaknesses in firewall rule-sets may allow certain types of ICMP (host unreachable, port unreachable) which are useful for UDP ping attempts.
• TCP SYN Ping CAPEC-299 An adversary uses TCP SYN packets as a means towards host discovery. Typical RFC 793 behavior specifies that when a TCP port is open, a host must respond to an incoming SYN "synchronize" packet by completing stage two of the 'three-way handshake' - by sending an SYN/ACK in response. When a port is closed, RFC 793 behavior is to respond with a RST "reset" packet. This behavior can be used to 'ping' a target to see if it is alive by sending a TCP SYN packet to a port and then looking for a RST or an ACK packet in response.
• Port Scanning CAPEC-300 An adversary uses a combination of techniques to determine the state of the ports on a remote target. Any service or application available for TCP or UDP networking will have a port open for communications over the network.
• TCP Connect Scan CAPEC-301 An adversary uses full TCP connection attempts to determine if a port is open on the target system. The scanning process involves completing a 'three-way handshake' with a remote port, and reports the port as closed if the full handshake cannot be established. An advantage of TCP connect scanning is that it works against any TCP/IP stack.
• TCP FIN Scan CAPEC-302 An adversary uses a TCP FIN scan to determine if ports are closed on the target machine. This scan type is accomplished by sending TCP segments with the FIN bit set in the packet header. The RFC 793 expected behavior is that any TCP segment with an out-of-state Flag sent to an open port is discarded, whereas segments with out-of-state flags sent to closed ports should be handled with a RST in response. This behavior should allow the adversary to scan for closed ports by sending certain types of rule-breaking packets (out of sync or disallowed by the TCB) and detect closed ports via RST packets.
• TCP Xmas Scan CAPEC-303 An adversary uses a TCP XMAS scan to determine if ports are closed on the target machine. This scan type is accomplished by sending TCP segments with all possible flags set in the packet header, generating packets that are illegal based on RFC 793. The RFC 793 expected behavior is that any TCP segment with an out-of-state Flag sent to an open port is discarded, whereas segments with out-of-state flags sent to closed ports should be handled with a RST in response. This behavior should allow an attacker to scan for closed ports by sending certain types of rule-breaking packets (out of sync or disallowed by the TCB) and detect closed ports via RST packets.
• TCP Null Scan CAPEC-304 An adversary uses a TCP NULL scan to determine if ports are closed on the target machine. This scan type is accomplished by sending TCP segments with no flags in the packet header, generating packets that are illegal based on RFC 793. The RFC 793 expected behavior is that any TCP segment with an out-of-state Flag sent to an open port is discarded, whereas segments with out-of-state flags sent to closed ports should be handled with a RST in response. This behavior should allow an attacker to scan for closed ports by sending certain types of rule-breaking packets (out of sync or disallowed by the TCB) and detect closed ports via RST packets.
• TCP ACK Scan CAPEC-305 An adversary uses TCP ACK segments to gather information about firewall or ACL configuration. The purpose of this type of scan is to discover information about filter configurations rather than port state. This type of scanning is rarely useful alone, but when combined with SYN scanning, gives a more complete picture of the type of firewall rules that are present.
• TCP Window Scan CAPEC-306 An adversary engages in TCP Window scanning to analyze port status and operating system type. TCP Window scanning uses the ACK scanning method but examine the TCP Window Size field of response RST packets to make certain inferences. While TCP Window Scans are fast and relatively stealthy, they work against fewer TCP stack implementations than any other type of scan. Some operating systems return a positive TCP window size when a RST packet is sent from an open port, and a negative value when the RST originates from a closed port. TCP Window scanning is one of the most complex scan types, and its results are difficult to interpret. Window scanning alone rarely yields useful information, but when combined with other types of scanning is more useful. It is a generally more reliable means of making inference about operating system versions than port status.
• TCP RPC Scan CAPEC-307 An adversary scans for RPC services listing on a Unix/Linux host.
• UDP Scan CAPEC-308 An adversary engages in UDP scanning to gather information about UDP port status on the target system. UDP scanning methods involve sending a UDP datagram to the target port and looking for evidence that the port is closed. Open UDP ports usually do not respond to UDP datagrams as there is no stateful mechanism within the protocol that requires building or establishing a session. Responses to UDP datagrams are therefore application specific and cannot be relied upon as a method of detecting an open port. UDP scanning relies heavily upon ICMP diagnostic messages in order to determine the status of a remote port.
• Network Topology Mapping CAPEC-309 An adversary engages in scanning activities to map network nodes, hosts, devices, and routes. Adversaries usually perform this type of network reconnaissance during the early stages of attack against an external network. Many types of scanning utilities are typically employed, including ICMP tools, network mappers, port scanners, and route testing utilities such as traceroute.
• Scanning for Vulnerable Software CAPEC-310 An attacker engages in scanning activity to find vulnerable software versions or types, such as operating system versions or network services. Vulnerable or exploitable network configurations, such as improperly firewalled systems, or misconfigured systems in the DMZ or external network, provide windows of opportunity for an attacker. Common types of vulnerable software include unpatched operating systems or services (e.g FTP, Telnet, SMTP, SNMP) running on open ports that the attacker has identified. Attackers usually begin probing for vulnerable software once the external network has been port scanned and potential targets have been revealed.
• Active OS Fingerprinting CAPEC-312 An adversary engages in activity to detect the operating system or firmware version of a remote target by interrogating a device, server, or platform with a probe designed to solicit behavior that will reveal information about the operating systems or firmware in the environment. Operating System detection is possible because implementations of common protocols (Such as IP or TCP) differ in distinct ways. While the implementation differences are not sufficient to 'break' compatibility with the protocol the differences are detectable because the target will respond in unique ways to specific probing activity that breaks the semantic or logical rules of packet construction for a protocol. Different operating systems will have a unique response to the anomalous input, providing the basis to fingerprint the OS behavior. This type of OS fingerprinting can distinguish between operating system types and versions.
• Passive OS Fingerprinting CAPEC-313 An adversary engages in activity to detect the version or type of OS software in a an environment by passively monitoring communication between devices, nodes, or applications. Passive techniques for operating system detection send no actual probes to a target, but monitor network or client-server communication between nodes in order to identify operating systems based on observed behavior as compared to a database of known signatures or values. While passive OS fingerprinting is not usually as reliable as active methods, it is generally better able to evade detection.
• IP ID Sequencing Probe CAPEC-317 This OS fingerprinting probe analyzes the IP 'ID' field sequence number generation algorithm of a remote host. Operating systems generate IP 'ID' numbers differently, allowing an attacker to identify the operating system of the host by examining how is assigns ID numbers when generating response packets. RFC 791 does not specify how ID numbers are chosen or their ranges, so ID sequence generation differs from implementation to implementation. There are two kinds of IP 'ID' sequence number analysis - IP 'ID' Sequencing: analyzing the IP 'ID' sequence generation algorithm for one protocol used by a host and Shared IP 'ID' Sequencing: analyzing the packet ordering via IP 'ID' values spanning multiple protocols, such as between ICMP and TCP.
• IP 'ID' Echoed Byte-Order Probe CAPEC-318 This OS fingerprinting probe tests to determine if the remote host echoes back the IP 'ID' value from the probe packet. An attacker sends a UDP datagram with an arbitrary IP 'ID' value to a closed port on the remote host to observe the manner in which this bit is echoed back in the ICMP error message. The identification field (ID) is typically utilized for reassembling a fragmented packet. Some operating systems or router firmware reverse the bit order of the ID field when echoing the IP Header portion of the original datagram within an ICMP error message.
• IP (DF) 'Don't Fragment Bit' Echoing Probe CAPEC-319 This OS fingerprinting probe tests to determine if the remote host echoes back the IP 'DF' (Don't Fragment) bit in a response packet. An attacker sends a UDP datagram with the DF bit set to a closed port on the remote host to observe whether the 'DF' bit is set in the response packet. Some operating systems will echo the bit in the ICMP error message while others will zero out the bit in the response packet.
• TCP Timestamp Probe CAPEC-320 This OS fingerprinting probe examines the remote server's implementation of TCP timestamps. Not all operating systems implement timestamps within the TCP header, but when timestamps are used then this provides the attacker with a means to guess the operating system of the target. The attacker begins by probing any active TCP service in order to get response which contains a TCP timestamp. Different Operating systems update the timestamp value using different intervals. This type of analysis is most accurate when multiple timestamp responses are received and then analyzed. TCP timestamps can be found in the TCP Options field of the TCP header.
• TCP Sequence Number Probe CAPEC-321 This OS fingerprinting probe tests the target system's assignment of TCP sequence numbers. One common way to test TCP Sequence Number generation is to send a probe packet to an open port on the target and then compare the how the Sequence Number generated by the target relates to the Acknowledgement Number in the probe packet. Different operating systems assign Sequence Numbers differently, so a fingerprint of the operating system can be obtained by categorizing the relationship between the acknowledgement number and sequence number as follows: 1) the Sequence Number generated by the target is Zero, 2) the Sequence Number generated by the target is the same as the acknowledgement number in the probe, 3) the Sequence Number generated by the target is the acknowledgement number plus one, or 4) the Sequence Number is any other non-zero number.
• TCP (ISN) Greatest Common Divisor Probe CAPEC-322 This OS fingerprinting probe sends a number of TCP SYN packets to an open port of a remote machine. The Initial Sequence Number (ISN) in each of the SYN/ACK response packets is analyzed to determine the smallest number that the target host uses when incrementing sequence numbers. This information can be useful for identifying an operating system because particular operating systems and versions increment sequence numbers using different values. The result of the analysis is then compared against a database of OS behaviors to determine the OS type and/or version.
• TCP (ISN) Counter Rate Probe CAPEC-323 This OS detection probe measures the average rate of initial sequence number increments during a period of time. Sequence numbers are incremented using a time-based algorithm and are susceptible to a timing analysis that can determine the number of increments per unit time. The result of this analysis is then compared against a database of operating systems and versions to determine likely operation system matches.
• TCP (ISN) Sequence Predictability Probe CAPEC-324 This type of operating system probe attempts to determine an estimate for how predictable the sequence number generation algorithm is for a remote host. Statistical techniques, such as standard deviation, can be used to determine how predictable the sequence number generation is for a system. This result can then be compared to a database of operating system behaviors to determine a likely match for operating system and version.
• TCP Congestion Control Flag (ECN) Probe CAPEC-325 This OS fingerprinting probe checks to see if the remote host supports explicit congestion notification (ECN) messaging. ECN messaging was designed to allow routers to notify a remote host when signal congestion problems are occurring. Explicit Congestion Notification messaging is defined by RFC 3168. Different operating systems and versions may or may not implement ECN notifications, or may respond uniquely to particular ECN flag types.
• TCP Initial Window Size Probe CAPEC-326 This OS fingerprinting probe checks the initial TCP Window size. TCP stacks limit the range of sequence numbers allowable within a session to maintain the "connected" state within TCP protocol logic. The initial window size specifies a range of acceptable sequence numbers that will qualify as a response to an ACK packet within a session. Various operating systems use different Initial window sizes. The initial window size can be sampled by establishing an ordinary TCP connection.
• TCP Options Probe CAPEC-327 This OS fingerprinting probe analyzes the type and order of any TCP header options present within a response segment. Most operating systems use unique ordering and different option sets when options are present. RFC 793 does not specify a required order when options are present, so different implementations use unique ways of ordering or structuring TCP options. TCP options can be generated by ordinary TCP traffic.
• TCP 'RST' Flag Checksum Probe CAPEC-328 This OS fingerprinting probe performs a checksum on any ASCII data contained within the data portion or a RST packet. Some operating systems will report a human-readable text message in the payload of a 'RST' (reset) packet when specific types of connection errors occur. RFC 1122 allows text payloads within reset packets but not all operating systems or routers implement this functionality.
• ICMP Error Message Quoting Probe CAPEC-329 An adversary uses a technique to generate an ICMP Error message (Port Unreachable, Destination Unreachable, Redirect, Source Quench, Time Exceeded, Parameter Problem) from a target and then analyze the amount of data returned or "Quoted" from the originating request that generated the ICMP error message.
• ICMP Error Message Echoing Integrity Probe CAPEC-330 An adversary uses a technique to generate an ICMP Error message (Port Unreachable, Destination Unreachable, Redirect, Source Quench, Time Exceeded, Parameter Problem) from a target and then analyze the integrity of data returned or "Quoted" from the originating request that generated the error message.
• Browser Fingerprinting CAPEC-472 An attacker carefully crafts small snippets of Java Script to efficiently detect the type of browser the potential victim is using. Many web-based attacks need prior knowledge of the web browser including the version of browser to ensure successful exploitation of a vulnerability. Having this knowledge allows an attacker to target the victim with attacks that specifically exploit known or zero day weaknesses in the type and version of the browser used by the victim. Automating this process via Java Script as a part of the same delivery system used to exploit the browser is considered more efficient as the attacker can supply a browser fingerprinting method and integrate it with exploit code, all contained in Java Script and in response to the same web page request by the browser.
• File Discovery CAPEC-497 An adversary engages in probing and exploration activities to determine if common key files exists. Such files often contain configuration and security parameters of the targeted application, system or network. Using this knowledge may often pave the way for more damaging attacks.
• Shoulder Surfing CAPEC-508 In a shoulder surfing attack, an adversary observes an unaware individual's keystrokes, screen content, or conversations with the goal of obtaining sensitive information. One motive for this attack is to obtain sensitive information about the target for financial, personal, political, or other gains. From an insider threat perspective, an additional motive could be to obtain system/application credentials or cryptographic keys. Shoulder surfing attacks are accomplished by observing the content "over the victim's shoulder", as implied by the name of this attack.
• Process Footprinting CAPEC-573 An adversary exploits functionality meant to identify information about the currently running processes on the target system to an authorized user. By knowing what processes are running on the target system, the adversary can learn about the target environment as a means towards further malicious behavior.
• Services Footprinting CAPEC-574 An adversary exploits functionality meant to identify information about the services on the target system to an authorized user. By knowing what services are registered on the target system, the adversary can learn about the target environment as a means towards further malicious behavior. Depending on the operating system, commands that can obtain services information include "sc" and "tasklist/svc" using Tasklist, and "net start" using Net.
• Account Footprinting CAPEC-575 An adversary exploits functionality meant to identify information about the domain accounts and their permissions on the target system to an authorized user. By knowing what accounts are registered on the target system, the adversary can inform further and more targeted malicious behavior. Example Windows commands which can acquire this information are: "net user" and "dsquery".
• Group Permission Footprinting CAPEC-576 An adversary exploits functionality meant to identify information about user groups and their permissions on the target system to an authorized user. By knowing what users/permissions are registered on the target system, the adversary can inform further and more targeted malicious behavior. An example Windows command which can list local groups is "net localgroup".
• Owner Footprinting CAPEC-577 An adversary exploits functionality meant to identify information about the primary users on the target system to an authorized user. They may do this, for example, by reviewing logins or file modification times. By knowing what owners use the target system, the adversary can inform further and more targeted malicious behavior. An example Windows command that may accomplish this is "dir /A ntuser.dat". Which will display the last modified time of a user's ntuser.dat file when run within the root folder of a user. This time is synonymous with the last time that user was logged in.
• Session Credential Falsification through Prediction CAPEC-59 This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
• Reusing Session IDs (aka Session Replay) CAPEC-60 This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.
• Establish Rogue Location CAPEC-616 An adversary provides a malicious version of a resource at a location that is similar to the expected location of a legitimate resource. After establishing the rogue location, the adversary waits for a victim to visit the location and access the malicious resource.
• Identify Shared Files/Directories on System CAPEC-643 An adversary discovers connections between systems by exploiting the target system's standard practice of revealing them in searchable, common areas. Through the identification of shared folders/drives between systems, the adversary may further their goals of locating and collecting sensitive information/files, or map potential routes for lateral movement within the network.
• Peripheral Footprinting CAPEC-646 Adversaries may attempt to obtain information about attached peripheral devices and components connected to a computer system. Examples may include discovering the presence of iOS devices by searching for backups, analyzing the Windows registry to determine what USB devices have been connected, or infecting a victim system with malware to report when a USB device has been connected. This may allow the adversary to gain additional insight about the system or network environment, which may be useful in constructing further attacks.
• Eavesdropping CAPEC-651 An adversary intercepts a form of communication (e.g. text, audio, video) by way of software (e.g., microphone and audio recording application), hardware (e.g., recording equipment), or physical means (e.g., physical proximity). The goal of eavesdropping is typically to gain unauthorized access to sensitive information about the target for financial, personal, political, or other gains. Eavesdropping is different from a sniffing attack as it does not take place on a network-based communication channel (e.g., IP traffic). Instead, it entails listening in on the raw audio source of a conversation between two or more parties.
• Using Slashes in Alternate Encoding CAPEC-79 This attack targets the encoding of the Slash characters. An adversary would try to exploit common filtering problems related to the use of the slashes characters to gain access to resources on the target host. Directory-driven systems, such as file systems and databases, typically use the slash character to indicate traversal between directories or other container components. For murky historical reasons, PCs (and, as a result, Microsoft OSs) choose to use a backslash, whereas the UNIX world typically makes use of the forward slash. The schizophrenic result is that many MS-based systems are required to understand both forms of the slash. This gives the adversary many opportunities to discover and abuse a number of common filtering problems. The goal of this pattern is to discover server software that only applies filters to one version, but not the other.

Vulnerable Configurations

• cpe:2.3:a:hapijs:hapi:0.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.0.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.0.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.0.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.0.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.0.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.0.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.0.5:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.0.5:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.0.6:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.0.6:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.1.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.1.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.1.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.1.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.1.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.1.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.2.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.2.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.2.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.2.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.3.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.3.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.4.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.4.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.4.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.4.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.4.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.4.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.4.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.4.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.4.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.4.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.5.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.5.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.5.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.5.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.5.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.5.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.6.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.6.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.6.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.6.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.7.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.7.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.7.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.7.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.8.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.8.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.8.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.8.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.8.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.8.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.8.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.8.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.8.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.8.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.9.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.9.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.9.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.9.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.9.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.9.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.10.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.10.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.10.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.10.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.11.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.11.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.11.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.11.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.11.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.11.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.11.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.11.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.11.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.11.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.12.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.12.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.13.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.13.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.13.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.13.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.13.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.13.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.13.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.13.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.14.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.14.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.14.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.14.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.14.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.14.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.5:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.5:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.6:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.6:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.7:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.7:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.8:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.8:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.15.9:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.15.9:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:0.16.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:0.16.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.0.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.0.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.0.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.0.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.2.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.2.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.3.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.3.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.4.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.4.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.5.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.5.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.6.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.6.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.6.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.6.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.6.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.6.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.7.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.7.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.7.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.7.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.7.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.7.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.7.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.7.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.8.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.8.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.8.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.8.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.8.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.8.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.8.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.8.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.5:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.5:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.6:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.6:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.9.7:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.9.7:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.10.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.10.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.11.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.11.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.11.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.11.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.12.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.12.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.13.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.13.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.14.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.14.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.15.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.15.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.16.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.16.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.16.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.16.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.17.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.17.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.18.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.18.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.19.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.19.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.19.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.19.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.19.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.19.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.19.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.19.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.19.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.19.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.19.5:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.19.5:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:1.20.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:1.20.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.1.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.1.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.1.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.1.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.2.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.2.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.3.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.3.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.4.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.4.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.5.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.5.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:2.6.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:2.6.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:3.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:3.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:3.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:3.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:3.0.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:3.0.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:3.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:3.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.0.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.0.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.0.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.0.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.1.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.1.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.1.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.1.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.1.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.1.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:4.1.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:4.1.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:5.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:5.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:5.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:5.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.0.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.0.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.2.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.2.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.2.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.2.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.2.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.2.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.3.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.3.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.4.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.4.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.5.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.5.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.5.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.5.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.6.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.6.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.7.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.7.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.7.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.7.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.8.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.8.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.8.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.8.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.9.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.9.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.10.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.10.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.11.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.11.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:6.11.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:6.11.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.1.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.1.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.2.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.2.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.3.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.3.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.4.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.4.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.5.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.5.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.5.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.5.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.5.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.5.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:7.5.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:7.5.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.2.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.2.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.3.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.3.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.3.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.3.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.4.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.4.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.5.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.5.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.5.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.5.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.5.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.5.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.5.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.5.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.6.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.6.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.6.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.6.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.8.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.8.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:8.8.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:8.8.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.0.2:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.0.2:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.0.3:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.0.3:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.0.4:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.0.4:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.2.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.2.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.3.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.3.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.3.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.3.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:9.5.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:9.5.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:10.0.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:10.0.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:10.0.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:10.0.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:10.1.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:10.1.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:10.2.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:10.2.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:10.4.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:10.4.0:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:10.4.1:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:10.4.1:*:*:*:*:node.js:*:*
• cpe:2.3:a:hapijs:hapi:10.5.0:*:*:*:*:node.js:*:*
  cpe:2.3:a:hapijs:hapi:10.5.0:*:*:*:*:node.js:*:*

Other 5 Recently Published CVEs Vulnerabilities

• CVE-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
• CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
• CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
• CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
• CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...