Version 6.6.10

[ildyria]

No description provided.

[Copilot]

Pull Request Overview

This PR updates the announcement banner to highlight a critical security update and adds detailed release notes for version 6.6.10.

• Update Announcement.astro to warn about a high-severity vulnerability in v6.6.9
• Add v6.6.10 release entry in docs/releases.md including vulnerability description, remediation steps, and credits

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
src/components/widgets/Announcement.astro	Replace v6.6.9 link with v6.6.10 CVE warning; retain old block as comment
docs/releases.md	Append new section for v6.6.10 with security fix details and instructions

[Copilot]

[nitpick] Remove the commented-out anchor block (lines 12–15) to avoid dead code and reduce clutter; version control history preserves the previous link.

Suggested change

	<!-- <a
	href="https://github.com/LycheeOrg/Lychee/releases/tag/v6.6.10"
	class="text-slate-200 hover:underline dark:text-slate-200 font-medium">Lychee 6.6.10 is now available! »</a
	> -->

[d7415]

Suggested change

	This vulnerability miss-uses the `$path` variable sent to the server, which is used to access the photos via the `SecurePathController`.
	This vulnerability misuses the `$path` variable sent to the server, which is used to access the photos via the `SecurePathController`.

[d7415]

Suggested change

	When both the encrypted links and the temporary links are disabled, it is possible to call the endpoint with fictuous path values. Ironically, by enabling either of the functionality, the endpoint becomes secure again.
	When both the encrypted links and the temporary links are disabled, it is possible to call the endpoint with path values that are out of scope. Ironically, by enabling either of the functionality, the endpoint becomes secure again.

?

[d7415]

Suggested change

	1. when neither functionality are enabled, we direclty return a 401/403 error on any call to `/image/{path}`.
	1. when neither functionality is enabled, we directly return a 401/403 error on any call to `/image/{path}`.

[d7415]

Suggested change

	2. when either of the functionality are enabled, we check that the `$path` value generated by `Storage::disk(StorageDiskType::LOCAL->value)->path($path);` is within the intended image directory. Should this happen, we return a 418 error code (I'm a teapot) which can later be used to detect malicious calls and combined with fail-2-ban to block the IP address of the attacker.
	2. when either of the functionalities are enabled, we check that the `$path` value generated by `Storage::disk(StorageDiskType::LOCAL->value)->path($path);` is within the intended image directory. Should this happen, we return a 418 error code (I'm a teapot) which can later be used to detect malicious calls and combined with fail-2-ban to block the IP address of the attacker.