14.50.17.15 Threat Intelligence and Host Information

General

IP Address
14.50.17.15
IPv4 Address
Location
🇰🇷 Chungcheongnam-do, South Korea
KR
Network
AS4766
Korea Telecom
Threat Score
45/100
Medium Risk
abuseipdbBruteforceBrute-ForceportscanSSH
Attack Intelligence
MITRE ATT&CK Techniques
T1046 - Network Service Scanning
Open Ports Detected
111
Geographic Location
Country
South Korea
City
Chungcheongnam-do
Region
Chungcheongnam-do
Coordinates
36.5030, 127.0028
Network Information
ASN
AS4766
Organization
Korea Telecom
Network
AS4766 Korea Telecom
WHOIS Information
inetnum
14.32.0.0 - 14.95.255.255
netname
KORNET-KR
descr
Korea Telecom
admin-c
IA9-KR
tech-c
IM9-KR
country
KR
status
ALLOCATED PORTABLE
mnt-by
MNT-KRNIC-AP
mnt-irt
IRT-KRNIC-KR
last-modified
2017-03-28T06:37:04Z
irt
IRT-KRNIC-KR
address
KT Head Office
e-mail
kornet_ip@kt.com
abuse-mailbox
irt@nic.or.kr
person
IP Manager
phone
+82-2-500-6630
nic-hdl
IM9-KR
changed
hostmaster@nic.or.kr
Attack Logs
Date Target Location Protocol Link
2024-07-31 Digitaloceanfrankfurt SSH View Log

  • Country: South Korea
  • Network: AS4766 korea telecom
  • Noticed: 6 times
  • Protocols Attacked: ssh
  • Countries Attacked: Poland

CVEs Detected

CVE-2006-20001 CVE-2007-2768 CVE-2007-4723 CVE-2008-3844 CVE-2009-0796 CVE-2009-1390 CVE-2009-2299 CVE-2009-3765 CVE-2009-3766 CVE-2009-3767 CVE-2011-1176 CVE-2011-2688 CVE-2012-3526 CVE-2012-4001 CVE-2012-4360 CVE-2012-6708 CVE-2013-0941 CVE-2013-0942 CVE-2013-2765 CVE-2013-4365 CVE-2015-8325 CVE-2015-9251 CVE-2016-0736 CVE-2016-0777 CVE-2016-0778 CVE-2016-10009 CVE-2016-10010 CVE-2016-10011 CVE-2016-10012 CVE-2016-10708 CVE-2016-1907 CVE-2016-1908 CVE-2016-20012 CVE-2016-2161 CVE-2016-2177 CVE-2016-2178 CVE-2016-2179 CVE-2016-2180 CVE-2016-2181 CVE-2016-2182 CVE-2016-2183 CVE-2016-3115 CVE-2016-4800 CVE-2016-4975 CVE-2016-4979 CVE-2016-5387 CVE-2016-6210 CVE-2016-6302 CVE-2016-6303 CVE-2016-6304 CVE-2016-6306 CVE-2016-6515 CVE-2016-7055 CVE-2016-8610 CVE-2016-8612 CVE-2016-8740 CVE-2016-8743 CVE-2016-8858 CVE-2017-15710 CVE-2017-15715 CVE-2017-15906 CVE-2017-3167 CVE-2017-3169 CVE-2017-3731 CVE-2017-3732 CVE-2017-3735 CVE-2017-3736 CVE-2017-3737 CVE-2017-3738 CVE-2017-7656 CVE-2017-7657 CVE-2017-7658 CVE-2017-7679 CVE-2017-9735 CVE-2017-9788 CVE-2017-9798 CVE-2018-0732 CVE-2018-0734 CVE-2018-0737 CVE-2018-0739 CVE-2018-11763 CVE-2018-12536 CVE-2018-12545 CVE-2018-1283 CVE-2018-1301 CVE-2018-1302 CVE-2018-1303 CVE-2018-1312 CVE-2018-1333 CVE-2018-15473 CVE-2018-15919 CVE-2018-17189 CVE-2018-17199 CVE-2018-20685 CVE-2018-5407 CVE-2019-0196 CVE-2019-0211 CVE-2019-0217 CVE-2019-0220 CVE-2019-10081 CVE-2019-10082 CVE-2019-10092 CVE-2019-10098 CVE-2019-10241 CVE-2019-10247 CVE-2019-11358 CVE-2019-1547 CVE-2019-1551 CVE-2019-1552 CVE-2019-1559 CVE-2019-1563 CVE-2019-17567 CVE-2019-6109 CVE-2019-6110 CVE-2019-6111 CVE-2019-9517 CVE-2020-11022 CVE-2020-11023 CVE-2020-11985 CVE-2020-11993 CVE-2020-13938 CVE-2020-14145 CVE-2020-15778 CVE-2020-1927 CVE-2020-1934 CVE-2020-1968 CVE-2020-1971 CVE-2020-27216 CVE-2020-35452 CVE-2020-7656 CVE-2020-9490 CVE-2021-23840 CVE-2021-23841 CVE-2021-26690 CVE-2021-26691 CVE-2021-28165 CVE-2021-28169 CVE-2021-32785 CVE-2021-32786 CVE-2021-32791 CVE-2021-32792 CVE-2021-33193 CVE-2021-34428 CVE-2021-34798 CVE-2021-36368 CVE-2021-3712 CVE-2021-39275 CVE-2021-40438 CVE-2021-4160 CVE-2021-41617 CVE-2021-44224 CVE-2021-44790 CVE-2022-0778 CVE-2022-1292 CVE-2022-2047 CVE-2022-2048 CVE-2022-2068 CVE-2022-22719 CVE-2022-22720 CVE-2022-22721 CVE-2022-23943 CVE-2022-26377 CVE-2022-28330 CVE-2022-28614 CVE-2022-28615 CVE-2022-29404 CVE-2022-30556 CVE-2022-31813 CVE-2022-36760 CVE-2022-37436 CVE-2022-4304 CVE-2023-0215 CVE-2023-0286 CVE-2023-0464 CVE-2023-0465 CVE-2023-0466 CVE-2023-25690 CVE-2023-26048 CVE-2023-26049 CVE-2023-2650 CVE-2023-31122 CVE-2023-36478 CVE-2023-36479 CVE-2023-3817 CVE-2023-38408 CVE-2023-40167 CVE-2023-44487 CVE-2023-45802 CVE-2023-48795 CVE-2023-51385 CVE-2023-51767 CVE-2023-5678 CVE-2024-0727 CVE-2024-27316

Disclaimer
This page contains threat intelligence information for the IPv4 address 14.50.17.15 and was generated either as a result of observed malicious activity or as an information gathering exercise to assist with enrichment of security events and context. All information is gathered passively through aggregation of public sources, or observations through activity upon honeynets. The host score is calculated through a series of statistically weighted values and machine learning which takes into account metadata such as host information, frequency, volume and global distribution of malicious activity, association with other known malicious hosts or networks, proxying or anonymising behaviour such as with tor exit nodes, residential proxies or VPN services, and many other attributes. These values are historical and indicative only - and should not be taken to be an accurate representation of the users, businesses or networks in which they reside.