Vulnerability Scan Result

Target:

https://customer.gailgaspng.com/online/billpay

Scanned target: https://customer.gailgaspng.com/online/billpay

Submitted: Nov 05, 2025 from GQ

Public Scan

Scan mode: Passive (non-intrusive)

Summary

low

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Bill Pay
Description:	No description found

IP Information

ip_address	49.50.66.90
country	IN
network_name	Cyfuture India PVT Ltd
asn	AS55470

Open Ports

80/tcp	http	Microsoft IIS httpd -
443/tcp	https	Microsoft IIS httpd -
5060/tcp	sip	- -

Web Technologies

Software / Version	Category
Bootstrap \1	UI frameworks
toastr \1	JavaScript frameworks
Google Font API	Font scripts
jQuery	JavaScript libraries
Spin.js	JavaScript libraries
Microsoft ASP.NET	Web frameworks
HSTS	Security

Web Application Vulnerabilities

Evidence

URL	Method	Parameters	Evidence
https://customer.gailgaspng.com/online/billpay	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	Error message custom error message found in: `} else { // show custom error message based on input validity if (`

Vulnerability description

We noticed that the target application does not properly handle exceptional conditions, leading to error messages that reveal sensitive information.

Risk description

The risk is that an attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application.

Recommendation

It is recommended treating all exceptions of the application flow. Ensure that error messages only contain minimal details.

Classification

CWE	CWE-209
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://customer.gailgaspng.com/online/billpay	Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). 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-inline'' allows the execution of unsafe in-page scripts and event handlers. object-src: We recommend restricting object-src to 'none' only. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

https://customer.gailgaspng.com/online/billpay

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval(). 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-inline'' allows the execution of unsafe in-page scripts and event handlers. object-src: We recommend restricting object-src to 'none' only. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files.

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

Software / Version	Category
Bootstrap \1	UI frameworks
toastr \1	JavaScript frameworks
Google Font API	Font scripts
jQuery	JavaScript libraries
Spin.js	JavaScript libraries
Microsoft ASP.NET	Web frameworks
HSTS	Security

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	Method	Parameters	Evidence
https://customer.gailgaspng.com/online/billpay	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: gailcgdhelpline@gail.co.in gailgashelpline@gail.co.in

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

Infrastructure Vulnerabilities

Evidence

Software / Version	Category
Microsoft ASP.NET	Web frameworks
Bootstrap \1	UI frameworks
toastr \1	JavaScript frameworks
jQuery	JavaScript libraries
crypto-js	JavaScript libraries
Google Font API	Font scripts
Font Awesome	Font scripts
HSTS	Security

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.

Operating System	Accuracy
Microsoft Windows Server 2016	99%

Evidence

Domain Queried	DNS Record Type	Description	Value
customer.gailgaspng.com	A	IPv4 address	49.50.66.90

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.