Vulnerability Scan Result
| Title: | 【速報】岸和田市の永野前市長 “収賄罪”などで起訴 大阪地検特捜部｜FNNプライムオンライン |
| Description: | 大阪府岸和田市が発注した工事の入札をめぐり、便宜を図った見返りに賄賂を受けた疑いなどで逮捕された永野耕平前市長（47）がきょう＝14日、収賄などの罪で起訴されました。大阪地検特捜部によると、永野被告は市長を務めていた2021年と去年、公共工事の入札に先立ち最低制限価格を業者側に漏らし落札させたうえ、その見返りに業者側から3度にわたり計1900万円の融資を受け賄賂を受け取った罪に問われています。永野被告は、2021年の岸和田競輪場の整備工事の入札で同じ人物に最低制限価格を漏らして落札させたとして… |
| ip_address | 163.49.35.64 |
| country | JP  |
| network_name | Internet Initiative Japan Inc |
| asn | AS2497 |
80/tcp | http | - - |
443/tcp | https | - - |
| Software / Version | Category |
|---|---|
| Amazon Advertising | Advertising |
| cdnjs | CDN |
| Funding Choices | Cookie compliance |
| Google Publisher Tag | Advertising |
| Google Hosted Libraries | CDN |
| Google Analytics UA | Analytics |
| Integral Ad Science | Advertising |
| jQuery 3.5.1 | JavaScript libraries |
| Open Graph | Miscellaneous |
| Swiper | JavaScript libraries |
| PWA | Miscellaneous |
| Cloudflare | CDN |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| Outbrain | Widgets, Advertising |
| HSTS | Security |
| RSS | Miscellaneous |
| Treasure Data | Customer data platform |
| Cart Functionality | Ecommerce |
Web Application Vulnerabilities
Evidence
| URL | Evidence |
|---|---|
| https://www.fnn.jp/articles/-/945306 | 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 |
|---|---|
| https://www.fnn.jp/articles/-/945306 | 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 |
|---|---|
| Amazon Advertising | Advertising |
| cdnjs | CDN |
| Funding Choices | Cookie compliance |
| Google Publisher Tag | Advertising |
| Google Hosted Libraries | CDN |
| Google Analytics UA | Analytics |
| Integral Ad Science | Advertising |
| jQuery 3.5.1 | JavaScript libraries |
| Open Graph | Miscellaneous |
| Swiper | JavaScript libraries |
| PWA | Miscellaneous |
| Cloudflare | CDN |
| Google AdSense | Advertising |
| Google Tag Manager | Tag managers |
| jsDelivr | CDN |
| Outbrain | Widgets, Advertising |
| HSTS | Security |
| RSS | Miscellaneous |
| Treasure Data | Customer data platform |
| Cart Functionality | Ecommerce |
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
| URL | Method | Parameters | Evidence |
|---|---|---|---|
| https://www.fnn.jp/articles/-/945306 | GET | Headers: User-Agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/108.0.0.0 Safari/537.36 | Email Address: fnnjp.info@fujitv.co.jp |
Vulnerability description
We noticed that this web application exposes email addresses, which might be unintended. While not inherently a vulnerability, this information could be leveraged in social engineering or spam related activities.
Risk description
The risk is that exposed email addresses within the application could be accessed by unauthorized parties. This could lead to privacy violations, spam, phishing attacks, or other forms of misuse.
Recommendation
Compartmentalize the application to have 'safe' areas where trust boundaries can be unambiguously drawn. Do not allow email addresses to go outside of the trust boundary, and always be careful when interfacing with a compartment outside of the safe area.
Classification
| CWE | CWE-200 |
| OWASP Top 10 - 2017 | |
| OWASP Top 10 - 2021 |
Evidence
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.
Evidence
Vulnerability description
Website is accessible.
Infrastructure Vulnerabilities
Evidence
| Software / Version | Category |
|---|---|
| Cart Functionality | Ecommerce |
| Amazon Advertising | Advertising |
| HSTS | Security |
| Cloudflare | CDN |
| Swiper | JavaScript libraries |
| Outbrain | Widgets, Advertising |
| jsDelivr | CDN |
| jQuery 3.5.1 | JavaScript libraries |
| Google Tag Manager | Tag managers |
| Google Hosted Libraries | CDN |
| Google Analytics UA | Analytics |
| cdnjs | CDN |
| RSS | Miscellaneous |
| PWA | Miscellaneous |
| 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.
Evidence
| Operating System | Accuracy |
|---|---|
| OpenBSD 4.0 | 85% |
Vulnerability description
OS Detection
Evidence
| Domain Queried | DNS Record Type | Description | Value |
|---|---|---|---|
| www.fnn.jp | A | IPv4 address | 163.49.35.64 |
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.