Comment 0 for bug 2048103

This issue is being treated as a potential security risk under
embargo. Please do not make any public mention of embargoed
(private) security vulnerabilities before their coordinated
publication by the OpenStack Vulnerability Management Team in the
form of an official OpenStack Security Advisory. This includes
discussion of the bug or associated fixes in public forums such as
mailing lists, code review systems and bug trackers. Please also
avoid private disclosure to other individuals not already approved
for access to this information, and provide this same reminder to
those who are made aware of the issue prior to publication. All
discussion should remain confined to this private bug report, and
any proposed fixes should be added to the bug as attachments. This
embargo shall not extend past 2024-04-03 and will be made
public by or on that date even if no fix is identified.

Members of the VMT received the following report by E-mail:

Dear VMT

I have identified a vulnerability in the OpenStack system and would like to report it to the OpenStack Vulnerability Management Team.:

While using OpenStack, I attempted to edit an image and noticed that the web frontend interface restricts the character limit of the image description to 256 characters. However, when I intercepted the request using Burp Suite and filled the description with more than 256 characters, the server did not reject the request. Therefore, the frontend restriction is not enforced on the backend. This vulnerability could potentially allow an attacker to quickly fill up storage, leading to a denial-of-service (DoS) attack. Additionally, I want to mention that after discovering this issue, I tested other modules for similar problems and have not found any. Their frontend and backend implementations appear to be consistent.

Attached is a video demonstrating the reproduction of the vulnerability.