Shodan

185.132.36.53

Regular View Raw Data Timeline
Last Seen: 2025-02-14
Tags:
eol-product

GeneralInformation

Hostnames atlastk.com
bhs.atlastk.com
gra.atlastk.com
www.atlastk.com
atlastk.org
bhs.atlastk.org
gra.atlastk.org
grb.atlastk.org
www.atlastk.org
q37.info
bhs.q37.info
coder.q37.info
bhs.coder.q37.info
gra.coder.q37.info
grb.coder.q37.info
deu.q37.info
epeios.q37.info
bhs.epeios.q37.info
gra.epeios.q37.info
grb.epeios.q37.info
www.epeios.q37.info
faas.q37.info
faas-1.q37.info
faas-2.q37.info
faas-3.q37.info
bhs.faas.q37.info
gra.faas.q37.info
grb.faas.q37.info
faas1.q37.info
faas2.q37.info
gra.q37.info
grb.q37.info
ng.q37.info
bhs.ng.q37.info
gra.ng.q37.info
grb.ng.q37.info
ohes.q37.info
s.q37.info
bhs.s.q37.info
gra.s.q37.info
grb.s.q37.info
teaching.q37.info
bhs.teaching.q37.info
gra.teaching.q37.info
grb.teaching.q37.info
upload.q37.info
bhs.upload.q37.info
gra.upload.q37.info
grb.upload.q37.info
www.q37.info
zelbinium.q37.info
bhs.zelbinium.q37.info
gra.zelbinium.q37.info
grb.zelbinium.q37.info
Domains atlastk.com atlastk.org q37.info 
Country United Kingdom
City London
Organization UK Next Generation Cloud Server (NGCS)
ISP IONOS SE
ASN AS8560

Vulnerabilities

Note: the device may not be impacted by all of these issues. The vulnerabilities are implied based on the software and version.

2023(1)
CVE-2023-44487
7.5The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
2021(2)
CVE-2021-23017
7.7A security issue in nginx resolver was identified, which might allow an attacker who is able to forge UDP packets from the DNS server to cause 1-byte memory overwrite, resulting in worker process crash or potential other impact.
CVE-2021-3618
7.4ALPACA is an application layer protocol content confusion attack, exploiting TLS servers implementing different protocols but using compatible certificates, such as multi-domain or wildcard certificates. A MiTM attacker having access to victim's traffic at the TCP/IP layer can redirect traffic from one subdomain to another, resulting in a valid TLS session. This breaks the authentication of TLS and cross-protocol attacks may be possible where the behavior of one protocol service may compromise the other at the application layer.
2019(4)
CVE-2019-20372
5.3NGINX before 1.17.7, with certain error_page configurations, allows HTTP request smuggling, as demonstrated by the ability of an attacker to read unauthorized web pages in environments where NGINX is being fronted by a load balancer.
CVE-2019-9516
7.5Some HTTP/2 implementations are vulnerable to a header leak, potentially leading to a denial of service. The attacker sends a stream of headers with a 0-length header name and 0-length header value, optionally Huffman encoded into 1-byte or greater headers. Some implementations allocate memory for these headers and keep the allocation alive until the session dies. This can consume excess memory.
CVE-2019-9513
7.5Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service. The attacker creates multiple request streams and continually shuffles the priority of the streams in a way that causes substantial churn to the priority tree. This can consume excess CPU.
CVE-2019-9511
7.5Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service. The attacker requests a large amount of data from a specified resource over multiple streams. They manipulate window size and stream priority to force the server to queue the data in 1-byte chunks. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
2018(1)
CVE-2018-16845
8.2nginx before versions 1.15.6, 1.14.1 has a vulnerability in the ngx_http_mp4_module, which might allow an attacker to cause infinite loop in a worker process, cause a worker process crash, or might result in worker process memory disclosure by using a specially crafted mp4 file. The issue only affects nginx if it is built with the ngx_http_mp4_module (the module is not built by default) and the .mp4. directive is used in the configuration file. Further, the attack is only possible if an attacker is able to trigger processing of a specially crafted mp4 file with the ngx_http_mp4_module.

OpenPorts

80 / tcp
1651973090 | 2025-02-13T22:44:42.360328
443 / tcp
1651973090 | 2025-02-14T03:39:13.542376



Products
Pricing
Contact Us

Shodan ® - All rights reserved