floci-io Floci up to 2.1.0 S3 Destination Configuration DeliveryStreamDescription.java S3Destination.bucketName BucketARN path traversal

Summaryinfo

A vulnerability has been found in floci-io Floci up to 2.1.0 and classified as critical. The impacted element is the function S3Destination.bucketName of the file services/firehose/model/DeliveryStreamDescription.java of the component S3 Destination Configuration Handler. Performing a manipulation of the argument BucketARN results in path traversal. This vulnerability was named CVE-2026-124509. The attack may be initiated remotely. In addition, an exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, was found in floci-io Floci up to 2.1.0. This affects the function S3Destination.bucketName of the file services/firehose/model/DeliveryStreamDescription.java of the component S3 Destination Configuration Handler. The manipulation of the argument BucketARN with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality, integrity, and availability.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-124509. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.

It is declared as proof-of-concept.

Upgrading to version 2.2.0 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch b986b95074ef524019be7af51e1df172e48faa4b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• floci-io

Name

• Floci

Version

• 2.0
• 2.1.0

License

• open-source

Website

• Product: https://github.com/floci-io/floci/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Submitinfo

Accepted

• Submit #1035485: floci-io Floci (local AWS emulator) 2.0.1 (the released tag `2.0.1` carries the same `DeliveryStreamDescription`, `FirehoseService`, `S3Service` and `S3CfnProvisioner` code; reviewed at commit a5ab1672f9305299e3b7a32d67ce12b1d89f1199, the 2.0.1 head) Path (by lucasg2g)

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion