Vulnerability Scan Result
| Title: | 스냅문 |
| Description: | 본식영상 아이폰 스냅 전문 업체 |
| ip_address | 65.9.66.39 |
| country | US  |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 65.9.66.31 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 65.9.66.58 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
| ip_address | 65.9.66.46 |
| country | US |
| network_name | Amazon Inc |
| asn | AS16509 |
80/tcp | http | Amazon CloudFront httpd - |
443/tcp | https | CloudFront - |
| Software / Version | Category |
|---|---|
| Naver Analytics | Analytics |
| Amazon Web Services | PaaS |
| Amazon CloudFront | CDN |
| Amazon S3 | CDN |
| Font Awesome | Font scripts |
| Froala Editor 2+ | Rich text editors |
| Bootstrap 3.4.1 | UI frameworks |
| Axios | JavaScript libraries |
| core-js 3.27.1 | JavaScript libraries |
| Chosen | JavaScript frameworks, Web frameworks |
| Imweb | Ecommerce |
| jQuery 1.12.4 | JavaScript libraries |
| jQuery UI 1.12.1 | JavaScript libraries |
| Slick | JavaScript libraries |
| Modernizr 2.6.2 | JavaScript libraries |
| Moment.js 2.10.3 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| NProgress 0.2.0 | JavaScript libraries |
| Sentry 9.12.0 | Issue trackers |
| Vimeo | Video players |
| Vue.js 3.5.13 | JavaScript frameworks |
| Lodash 4.17.15 | JavaScript libraries |
| YouTube | Video players |
Web Application Vulnerabilities
Evidence
| Risk Level | CVSS | CVE | Summary | Affected software |
|---|---|---|---|---|
| 7.8 | CVE-2016-4055 | The duration function in the moment package before 2.11.2 for Node.js allows remote attackers to cause a denial of service (CPU consumption) via a long string, aka a "regular expression Denial of Service (ReDoS)." | moment 2.10.3 | |
| 6.5 | CVE-2021-23337 | Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function. | lodash 4.17.15 | |
| 6.4 | CVE-2024-6484 | A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of an <a> tag due to inadequate sanitization. This vulnerability could potentially enable attackers to execute arbitrary JavaScript within the victim's browser. | bootstrap 3.4.1 | |
| 6.1 | CVE-2022-31160 | jQuery UI is a curated set of user interface interactions, effects, widgets, and themes built on top of jQuery. Versions prior to 1.13.2 are potentially vulnerable to cross-site scripting. Initializing a checkboxradio widget on an input enclosed within a label makes that parent label contents considered as the input label. Calling `.checkboxradio( "refresh" )` on such a widget and the initial HTML contained encoded HTML entities will make them erroneously get decoded. This can lead to potentially executing JavaScript code. The bug has been patched in jQuery UI 1.13.2. To remediate the issue, someone who can change the initial HTML can wrap all the non-input contents of the `label` in a `span`. | jquery_ui 1.12.1 | |
| 5.8 | CVE-2020-8203 | Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. | lodash 4.17.15 | |
| 5 | CVE-2017-18214 | The moment module before 2.19.3 for Node.js is prone to a regular expression denial of service via a crafted date string, a different vulnerability than CVE-2016-4055. | moment 2.10.3 | |
| 5 | CVE-2022-24785 | Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js. | moment 2.10.3 | |
| 5 | CVE-2020-28500 | Lodash versions prior to 4.17.21 are vulnerable to Regular Expression Denial of Service (ReDoS) via the toNumber, trim and trimEnd functions. | lodash 4.17.15 | |
| 4.3 | CVE-2021-41182 | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `altField` option of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `altField` option is now treated as a CSS selector. A workaround is to not accept the value of the `altField` option from untrusted sources. | jquery_ui 1.12.1 | |
| 4.3 | CVE-2021-41183 | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of various `*Text` options of the Datepicker widget from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. The values passed to various `*Text` options are now always treated as pure text, not HTML. A workaround is to not accept the value of the `*Text` options from untrusted sources. | jquery_ui 1.12.1 | |
| 4.3 | CVE-2021-41184 | jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources. | jquery_ui 1.12.1 | |
| 4.3 | CVE-2015-9251 | jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed. | jquery 1.12.4 | |
| 4.3 | CVE-2019-11358 | jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype. | jquery 1.12.4 | |
| 4.3 | CVE-2020-11023 | In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. | jquery 1.12.4 | |
| 4.3 | CVE-2020-11022 | In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0. | jquery 1.12.4 |
Vulnerability description
We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.
Risk description
The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.
Recommendation
In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.
Classification
| CWE | CWE-1026 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Response URL | Evidence |
|---|---|---|
| http://www.snapmoon.co.kr/ | http://www.snapmoon.co.kr/ | Communication is made over unsecure, unencrypted HTTP. |
Vulnerability description
We noticed that the communication between the web browser and the server is done using the HTTP protocol, which transmits data unencrypted over the network.
Risk description
The risk is that an attacker who manages to intercept the communication at the network level can read and modify the data transmitted (including passwords, secret tokens, credit card information and other sensitive data).
Recommendation
We recommend you to reconfigure the web server to use HTTPS - which encrypts the communication between the web browser and the server.
Classification
| CWE | CWE-311 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| http://www.snapmoon.co.kr/ | IMWEBVSSID, al | Set-Cookie: IMWEBVSSID=kv0g77g1grqi61ile3riajuaauegp4eo5trutjkl86f7j03rraf0q6iudr3kn6bb231t453a0vmm60vtg77rc3buka0toabp5159ob2 Set-Cookie: al=KR |
Vulnerability description
We found that a cookie has been set without the Secure flag, which means the browser will send it over an unencrypted channel (plain HTTP) if such a request is made. The root cause for this usually revolves around misconfigurations in the code or server settings.
Risk description
The risk exists that an attacker will intercept the clear-text communication between the browser and the server and he will steal the cookie of the user. If this is a session cookie, the attacker could gain unauthorized access to the victim's web session.
Recommendation
Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.
Classification
| CWE | CWE-614 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| http://www.snapmoon.co.kr/ | Response headers do not include the X-Content-Type-Options HTTP security header |
Vulnerability description
We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.
Risk description
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation
We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| http://www.snapmoon.co.kr/ | Response does not include the HTTP Content-Security-Policy security header or meta tag |
Vulnerability description
We noticed that the target application lacks the Content-Security-Policy (CSP) header in its HTTP responses. The CSP header is a security measure that instructs web browsers to enforce specific security rules, effectively preventing the exploitation of Cross-Site Scripting (XSS) vulnerabilities.
Risk description
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the application.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| http://www.snapmoon.co.kr/ | Response headers do not include the Referrer-Policy HTTP security header as well as the |
Vulnerability description
We noticed that the target application's server responses lack the Referrer-Policy HTTP header, which controls how much referrer information the browser will send with each request originated from the current web application.
Risk description
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g. "https://www.google.com", the browser will send to Google the full originating URL in the `Referer` header, assuming the Referrer-Policy header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value `no-referrer` of this header instructs the browser to omit the Referer header entirely.
Classification
| CWE | CWE-693 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| Software / Version | Category |
|---|---|
| Naver Analytics | Analytics |
| Amazon Web Services | PaaS |
| Amazon CloudFront | CDN |
| Amazon S3 | CDN |
| Font Awesome | Font scripts |
| Froala Editor 2+ | Rich text editors |
| Bootstrap 3.4.1 | UI frameworks |
| Axios | JavaScript libraries |
| core-js 3.27.1 | JavaScript libraries |
| Chosen | JavaScript frameworks, Web frameworks |
| Imweb | Ecommerce |
| jQuery 1.12.4 | JavaScript libraries |
| jQuery UI 1.12.1 | JavaScript libraries |
| Slick | JavaScript libraries |
| Modernizr 2.6.2 | JavaScript libraries |
| Moment.js 2.10.3 | JavaScript libraries |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| OWL Carousel | JavaScript libraries |
| NProgress 0.2.0 | JavaScript libraries |
| Sentry 9.12.0 | Issue trackers |
| Vimeo | Video players |
| Vue.js 3.5.13 | JavaScript frameworks |
| Lodash 4.17.15 | JavaScript libraries |
| YouTube | Video players |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
Vulnerability description
We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.
Risk description
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).
Evidence
Vulnerability description
Website is accessible.
Vulnerability description
We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.
Risk description
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.
Recommendation
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.
Infrastructure Vulnerabilities
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.snapmoon.co.kr | A | IPv4 address | 65.9.66.39 |
| www.snapmoon.co.kr | A | IPv4 address | 65.9.66.58 |
| www.snapmoon.co.kr | A | IPv4 address | 65.9.66.46 |
| www.snapmoon.co.kr | A | IPv4 address | 65.9.66.31 |
Risk description
An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.
Recommendation
We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.
Evidence
| Software / Version | Category |
|---|---|
| Imweb | Ecommerce |
| YouTube | Video players |
| Bootstrap | UI frameworks |
| Chosen | JavaScript frameworks, Web frameworks |
| Nginx | Web servers, Reverse proxies |
| Amazon Web Services | PaaS |
| Slick | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| Naver Analytics | Analytics |
| Moment.js | JavaScript libraries |
| Modernizr | JavaScript libraries |
| Lodash | JavaScript libraries |
| jQuery UI | JavaScript libraries |
| jQuery | JavaScript libraries |
| Amazon S3 | CDN |
| Amazon CloudFront | CDN |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.
Evidence
| Software / Version | Category |
|---|---|
| Imweb | Ecommerce |
| Sentry 9.12.0 | Issue trackers |
| Froala Editor 2+ | Rich text editors |
| Bootstrap | UI frameworks |
| Nginx | Web servers, Reverse proxies |
| YouTube | Video players |
| Chosen | JavaScript frameworks, Web frameworks |
| Vimeo | Video players |
| Amazon Web Services | PaaS |
| Vue.js 3.5.13 | JavaScript frameworks |
| Amazon S3 | CDN |
| Amazon CloudFront | CDN |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Slick | JavaScript libraries |
| OWL Carousel | JavaScript libraries |
| Naver Analytics | Analytics |
| Moment.js | JavaScript libraries |
| Modernizr | JavaScript libraries |
| Lodash | JavaScript libraries |
| jQuery UI | JavaScript libraries |
| jQuery | JavaScript libraries |
| Font Awesome | Font scripts |
| NProgress 0.2.0 | JavaScript libraries |
| core-js 3.27.1 | JavaScript libraries |
| Axios | JavaScript libraries |
| Open Graph | Miscellaneous |
Vulnerability description
We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.
Risk description
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.