Vulnerability Scan Result

Target:

http://www.ravelry.com/ (redirect)

Scanned target: https://www.ravelry.com/account/login

Submitted: Jul 02, 2025 from LB

Public Scan

Scan mode: Passive (non-intrusive)

Summary

high

Info

Low

Medium

High

Critical

Screenshot

Title:	Ravelry
Description:	No description found

IP Information

ip_address	192.34.84.3
country	US
network_name	Axcelx Technologies LLC
asn	AS33083

Open Ports

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

Web Technologies

Software / Version	Category
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
Plausible	Analytics
Sectigo	SSL/TLS certificate authorities
Prototype 1.5.1_rc2	JavaScript frameworks
HSTS	Security

Web Application Vulnerabilities

Evidence

Risk Level	CVSS	CVE	Summary	Affected software
	7.5	CVE-2008-7220	Unspecified vulnerability in Prototype JavaScript framework (prototypejs) before 1.6.0.2 allows attackers to make "cross-site ajax requests" via unknown vectors.	prototype 1.5.1

Vulnerability description

We noticed known vulnerabilities in the target application based on the server responses. They are usually related to outdated systems and expose the affected applications to the risk of unauthorized access to confidential data and possibly denial of service attacks. Depending on the system distribution the affected software can be patched but displays the same version, requiring manual checking.

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-1026
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Cookie Name	Evidence
https://www.ravelry.com/account/login	radvid, version	The server responded with Set-Cookie header(s) that does not specify the HttpOnly flag: Set-Cookie: radvid=e60315dcbb7791b835d31a326797a0ba Set-Cookie: version=1

Vulnerability description

We found that a cookie has been set without the HttpOnly flag, which means it can be accessed by potentially malicious JavaScript code running inside the web page. The root cause for this usually revolves around misconfigurations in the code or server settings.

Risk description

The risk is that an attacker who injects malicious JavaScript code on the page (e.g. by using an XSS attack) can access the cookie and can send it to another site. In case of a session cookie, this could lead to session hijacking.

Recommendation

Ensure that the HttpOnly flag is set for all cookies.

Classification

CWE	CWE-1004
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL	Evidence
https://www.ravelry.com/account/login	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://www.ravelry.com/account/login	Response headers do not include the X-Content-Type-Options HTTP security header

Vulnerability description

We noticed that the target application's server responses lack the X-Content-Type-Options header. This header is particularly important for preventing Internet Explorer from reinterpreting the content of a web page (MIME-sniffing) and thus overriding the value of the Content-Type header.

Risk description

The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.

Recommendation

We recommend setting the X-Content-Type-Options header such as `X-Content-Type-Options: nosniff`.

Classification

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

Evidence

URL Evidence

URL	Evidence
https://www.ravelry.com/account/login	Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none' only. 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: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

https://www.ravelry.com/account/login

Response headers include the HTTP Content-Security-Policy security header with the following security issues:object-src: We recommend restricting object-src to 'none' only. 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: 'self' can be problematic if you host JSONP, Angular or user uploaded files. default-src: The default-src directive should be set as a fall-back when other restrictions have not been specified. script-src: 'unsafe-eval' allows the execution of code injected into DOM APIs such as eval().

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
Nginx	Web servers, Reverse proxies
Open Graph	Miscellaneous
Plausible	Analytics
Sectigo	SSL/TLS certificate authorities
Prototype 1.5.1_rc2	JavaScript 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
https://www.ravelry.com/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

URL	Evidence
https://www.ravelry.com/account/login	`<input autocomplete="username" autofocus="autofocus" id="user_login" name="user[login]" size="30" type="text" value=""/> <input autocomplete="current-password" data-input-type="password" id="user_password" name="user[password]" size="30" type="password"/> <button class="clicker_v2 clicker_v2--standard clicker--large" type="submit">Log In</button>`

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.

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
www.ravelry.com	A	IPv4 address	192.34.84.3

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.

Operating System	Accuracy
Linux 4.4	100%

Evidence

Software / Version	Category
Nginx	Web servers, Reverse proxies
Plausible	Analytics
Sectigo	SSL/TLS certificate authorities
HSTS	Security
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.