Vulnerability Scan Result
| Title: | 転職をご希望の方｜株式会社ジップ |
| Description: | 株式会社ジップの採用情報サイト。中途採用、新卒採用の応募情報や、株式会社ジップのサービスや文化、環境などの情報を掲載しています。また社員インタビューで中の人の生の声も聞くことができます。 |
| ip_address | 57.180.95.204 |
| country | JP  |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
| ip_address | 52.68.171.253 |
| country | JP |
| network_name | Amazon.com, Inc. |
| asn | AS16509 |
80/tcp | http | awselb/2.0 - |
443/tcp | https | nginx - |
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon ELB | Load balancers |
| Google Analytics GA4 | Analytics |
| GSAP | JavaScript frameworks |
| jQuery 3.1.1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| ScrollMagic 2.0.7 | JavaScript libraries |
| DoubleClick Floodlight | Advertising |
| WordPress | CMS, Blogs |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| Zip | Payment processors, Buy now pay later |
Web Application Vulnerabilities
Evidence
| CVE | CVSS | EPSS Score | EPSS Percentile | Summary |
|---|---|---|---|---|
| CVE-2020-11023 | 6.9 | 0.66129 | 0.98531 | 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. |
| CVE-2020-11022 | 6.9 | 0.07042 | 0.91521 | In jQuery starting with 1.12.0 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. |
| CVE-2019-11358 | 6.1 | 0.02426 | 0.85198 | 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. |
Vulnerability description
Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.
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-1035 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Cookie Name | Evidence |
|---|---|---|
| https://recruit-zip.com:443/ | _app_session | Set-Cookie: _app_session=e3664d62d522ea70805d533fdaf2be27 |
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
| Software / Version | Category |
|---|---|
| Amazon Web Services | PaaS |
| AWS Certificate Manager | SSL/TLS certificate authorities |
| Amazon ELB | Load balancers |
| Google Analytics GA4 | Analytics |
| GSAP | JavaScript frameworks |
| jQuery 3.1.1 | JavaScript libraries |
| MySQL | Databases |
| Nginx | Web servers, Reverse proxies |
| Open Graph | Miscellaneous |
| PHP | Programming languages |
| Ruby | Programming languages |
| Ruby on Rails | Web frameworks |
| ScrollMagic 2.0.7 | JavaScript libraries |
| DoubleClick Floodlight | Advertising |
| WordPress | CMS, Blogs |
| Google Tag Manager | Tag managers |
| HSTS | Security |
| Zip | Payment processors, Buy now pay later |
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.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
| URL | Evidence |
|---|---|
| https://recruit-zip.com:443/ | 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-1021 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
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.
Classification
| CWE | CWE-1188 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Infrastructure Vulnerabilities
Evidence
We found insecure EDNS configuration on the following nameservers: ns-856.awsdns-43.net ns-856.awsdns-43.net:
Vulnerability description
We found that the server does not properly implement EDNS (Extension Mechanisms for DNS). EDNS allows larger DNS packets and supports modern features such as DNSSEC.
Risk description
The risk exists because improper or missing EDNS support can lead to truncated responses, degraded DNS performance, and compatibility issues with DNSSEC. This exposes users to risks such as incomplete DNS resolution and failed DNSSEC validation.
Recommendation
We recommend ensuring the proper implementation of EDNS on the DNS server. Update the DNS server software to support EDNS fully, including modern features like DNSSEC. Regularly test DNS configurations to ensure compliance and performance.
Evidence
We found insecure DNS cookie usage on the following nameservers: ns-1269.awsdns-30.org, ns-1787.awsdns-31.co.uk, ns-217.awsdns-27.com, ns-856.awsdns-43.net
Vulnerability description
We found that the server does not implement DNS Cookies or uses them insecurely. DNS Cookies help prevent DNS-based attacks, such as spoofing and amplification attacks.
Risk description
The risk exists because without DNS Cookies, the server is vulnerable to DNS spoofing and amplification attacks. Attackers can manipulate responses or use the server in distributed denial-of-service (DDoS) attacks, compromising network availability and security.
Recommendation
We recommend enabling DNS Cookies to prevent spoofed DNS responses. Ensure proper cookie validation is implemented to mitigate DNS amplification attacks. Regularly update DNS servers to support the latest DNS security features.
Evidence
| Software / Version | Category |
|---|---|
| WordPress | CMS, Blogs |
| Ruby | Programming languages |
| MySQL | Databases |
| PHP | Programming languages |
| Ruby on Rails | Web frameworks |
| Nginx | Web servers, Reverse proxies |
| Amazon ELB | Load balancers |
| Amazon Web Services | PaaS |
| Zip | Payment processors, Buy now pay later |
| Google Tag Manager | Tag managers |
| Google Analytics GA4 | Analytics |
| DoubleClick Floodlight | Advertising |
| HSTS | Security |
| AWS Certificate Manager | SSL/TLS certificate authorities |
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
| Operating System | Accuracy |
|---|---|
| Linux 2.6.32 | 90% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| recruit-zip.com | A | IPv4 address | 57.180.95.204 |
| recruit-zip.com | NS | Name server | ns-1269.awsdns-30.org |
| recruit-zip.com | NS | Name server | ns-1787.awsdns-31.co.uk |
| recruit-zip.com | NS | Name server | ns-217.awsdns-27.com |
| recruit-zip.com | NS | Name server | ns-856.awsdns-43.net |
| recruit-zip.com | SOA | Start of Authority | ns-1787.awsdns-31.co.uk. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400 |
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.