Vulnerability Scan Result

Target:

http://pms.aquachill.co.in/ (redirect)

Scanned target: https://pms.aquachill.co.in/

Submitted: Jan 28, 2026 from DO

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Screenshot could not be taken.

Title:	Sign In \| AquaChill
Description:	Aqua Chill Systems, based in Pune, India, specializes in offering cutting-edge solutions in HVAC, Process Cooling, CHPC Architecture, and Gas Turbine Inlet Air Cooling services.

IP Information

ip_address	103.158.54.99
country	IN
network_name	Infodex Solutions Pvt. Ltd.
asn	AS141338

Open Ports

443/tcp	tcpwrapped	- -
445/tcp	tcpwrapped	- -

Web Technologies

Software / Version	Category
Bootstrap	UI frameworks
Microsoft ASP.NET	Web frameworks

Web Application Vulnerabilities

Evidence

URL	Cookie Name	Evidence
https://pms.aquachill.co.in/	.AspNetCore.Antiforgery.tovl7-8vtms	Set-Cookie: .AspNetCore.Antiforgery.tovl7-8vtms=CfDJ8KjPUyODVD1AqVeHlZfyBb21cjhAkXC0WNqQuLzadEMA08Bp6Y0uQ86JDdMZcj3uvIItOiPeo0xbEAHhroSjfHW-eRMRxLXTNk3b6WuN-iWQqw9diwNYd_QKTDN1GlGSCFp6QWJscT3A1NZTkmc_PNY

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
Bootstrap	UI frameworks
Microsoft ASP.NET	Web frameworks

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
https://pms.aquachill.co.in/	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://pms.aquachill.co.in/	Response headers do not include the Referrer-Policy HTTP security header as well as the `<meta/>` tag with name 'referrer' is not present in the response.

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

URL	Evidence
https://pms.aquachill.co.in/	Response headers do not include the HTTP Strict-Transport-Security header

Vulnerability description

We noticed that the target application lacks the HTTP Strict-Transport-Security header in its responses. This security header is crucial as it instructs browsers to only establish secure (HTTPS) connections with the web server and reject any HTTP connections.

Risk description

The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).

Recommendation

The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows: `Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]` The parameter `max-age` gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months. A value below 7776000 is considered as too low by this scanner check. The flag `includeSubDomains` defines that the policy applies also for sub domains of the sender of the response.

Classification

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

Evidence

URL Evidence

URL	Evidence
https://pms.aquachill.co.in/	<input class="form-control" data-val="true" data-val-maxlength="User Id can't be more than 125 characters" data-val-maxlength-max="125" data-val-required="User Id is required" id="username" maxlength="125" name="UserId" placeholder="Enter username" type="text" value=""> <input class="form-control pe-5 password-input" data-val="true" data-val-maxlength="Password can't be more than 40 characters" data-val-maxlength-max="40" data-val-regex="Password has to be of min 6 chars and contain at least 1 capital and 1 special chars." data-val-regex-pattern="^.(?=.[A-Z])(?=.[@#$%^&+=]).$" data-val-required="Password is required" id="password-input" maxlength="40" name="Password" placeholder="Enter password" type="password" value=""> <button class="btn btn-success w-100" type="submit">Sign In</button>

https://pms.aquachill.co.in/

Vulnerability description

We have discovered that the target application presents a login interface that could be a potential target for attacks. While login interfaces are standard for user authentication, they can become vulnerabilities if not properly secured.

Risk description

The risk is that an attacker could use this interface to mount brute force attacks against known passwords and usernames combinations leaked throughout the web.

Recommendation

Ensure each interface is not bypassable using common knowledge of the application or leaked credentials using occasional password audits.

Evidence

URL	Method	Summary
https://pms.aquachill.co.in/	OPTIONS	We did a HTTP OPTIONS request. The server responded with a 405 status code and the header: `Allow: GET, POST` Request / Response

Vulnerability description

We have noticed that the webserver responded with an Allow HTTP header when an OPTIONS HTTP request was sent. This method responds to requests by providing information about the methods available for the target resource.

Risk description

The only risk this might present nowadays is revealing debug HTTP methods that can be used on the server. This can present a danger if any of those methods can lead to sensitive information, like authentication information, secret keys.

Recommendation

We recommend that you check for unused HTTP methods or even better, disable the OPTIONS method. This can be done using your webserver configuration.

Classification

CWE	CWE-16
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
Missing: https://pms.aquachill.co.in/.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
pms.aquachill.co.in	A	IPv4 address	103.158.54.99

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.