Vulnerability Scan Result

Target:

https://newsdig.tbs.co.jp/articles/-/2294622?display=1

Scanned target: https://newsdig.tbs.co.jp/articles/-/2294622?display=1

Submitted: Nov 18, 2025 from BF

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	17歳少年が「弁護士」になりすまし高齢者宅を訪問　現金100万円をだまし取ろうとした容疑で少年2人を逮捕　【岡山】 \| TBS NEWS DIG (1ページ)
Description:	息子などになりすまして、高齢者から現金をだましとろうとしたとして、特殊詐欺グループの少年2人が、きのう（17日）逮捕されました。詐欺未遂の容疑で逮捕されたのは、福岡市の無職の少年（17）と住所不詳の無職… (1ページ)

IP Information

ip_address	163.49.35.137
country	JP
network_name	Internet Initiative Japan Inc
asn	AS2497

Open Ports

80/tcp	http	- -
443/tcp	https	- -

Web Technologies

Software / Version	Category
Twitter Ads	Advertising
Amazon Advertising	Advertising
Lozad.js	JavaScript libraries, Performance
AppNexus	Advertising
jQuery CDN	CDN
Funding Choices	Cookie compliance
Google Publisher Tag	Advertising
DoubleVerify	Advertising, Analytics
Facebook Pixel 2.9.242	Analytics
Axios	JavaScript libraries
petite-vue	Miscellaneous
core-js 3.32.2	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
ID5	Advertising
jQuery 3.6.0	JavaScript libraries
Open Graph	Miscellaneous
OpenX	Advertising
Prebid 9.41.0	Advertising
Rubicon Project	Advertising
PWA	Miscellaneous
Google AdSense	Advertising
Google Tag Manager	Tag managers
PubMatic	Advertising
HSTS	Security
YouTube	Video players

Web Application Vulnerabilities

Evidence

URL
https://newsdig.tbs.co.jp/robots.txt

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

Software / Version	Category
Twitter Ads	Advertising
Amazon Advertising	Advertising
Lozad.js	JavaScript libraries, Performance
AppNexus	Advertising
jQuery CDN	CDN
Funding Choices	Cookie compliance
Google Publisher Tag	Advertising
DoubleVerify	Advertising, Analytics
Facebook Pixel 2.9.242	Analytics
Axios	JavaScript libraries
petite-vue	Miscellaneous
core-js 3.32.2	JavaScript libraries
Google Analytics	Analytics
Google Font API	Font scripts
ID5	Advertising
jQuery 3.6.0	JavaScript libraries
Open Graph	Miscellaneous
OpenX	Advertising
Prebid 9.41.0	Advertising
Rubicon Project	Advertising
PWA	Miscellaneous
Google AdSense	Advertising
Google Tag Manager	Tag managers
PubMatic	Advertising
HSTS	Security
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

URL Evidence

URL	Evidence
https://newsdig.tbs.co.jp/articles/-/2294622	Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: data: URI in default-src allows the execution of unsafe scripts.

https://newsdig.tbs.co.jp/articles/-/2294622

Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none'. script-src: ''unsafe-inline'' allows the execution of unsafe in-page scripts and event handlers. base-uri: Missing base-uri allows the injection of base tags. They can be used to set the base URL for all relative (script) URLs to an attacker controlled domain. We recommend setting it to 'none' or 'self'. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). default-src: default-src should not allow '*' as source. This may enable execution of malicious JavaScript. default-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: data: URI in default-src allows the execution of unsafe scripts.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

CWE	CWE-693
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://newsdig.tbs.co.jp/.well-known/security.txt

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
newsdig.tbs.co.jp	A	IPv4 address	163.49.35.137
newsdig.tbs.co.jp	MX	Mail server	10 alt4.aspmx.l.google.com
newsdig.tbs.co.jp	MX	Mail server	5 alt1.aspmx.l.google.com
newsdig.tbs.co.jp	MX	Mail server	5 alt2.aspmx.l.google.com
newsdig.tbs.co.jp	MX	Mail server	10 alt3.aspmx.l.google.com
newsdig.tbs.co.jp	MX	Mail server	1 aspmx.l.google.com
newsdig.tbs.co.jp	TXT	Text record	"google-site-verification=hvSX3qwWqSh4tg8-s3ZgZHHizpJIiGwheNGm1AABBKU"
newsdig.tbs.co.jp	SPF	Sender Policy Framework	"v=spf1 include:_spf.google.com ~all"

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
YouTube	Video players
Amazon Advertising	Advertising
Google Analytics	Analytics
HSTS	Security
jQuery CDN	CDN
jQuery 3.6.0	JavaScript libraries
Google Tag Manager	Tag managers
petite-vue	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.