Input validation missing on import csv functionality

[filipposfwt]

Issue

When importing a new standard, no validation is performed on the imported csv file, a generic non-descriptive "500 - Internal Server Error" is returned or new CREs are wrongfully injected.

More specifically, in the outlined case, if the format of "CRE 0" column is XX-XXX| instead of XXX-XXX|, a non-descriptive error is returned. Also, I noticed that if in the "<standard_name>|name" column the requirement's text is enclosed between three double quotes '"""', the csv is treated as valid and the whole row is entered as a new root CRE.

[Hardik301002]

Hi ,@northdpole , @filipposfwt

I have reviewed the issue and identified the missing input validation in the CSV import functionality. I plan to implement validation checks for headers, data formats, and security measures (such as preventing CSV injection). I will also ensure proper error handling and testing before submitting a fix.

Please assign this issue to me so I can start working on it. Let me know if you have any specific requirements or suggestions.

Thanks!

[northdpole]

@Hardik301002 just assigned

[sd2604]

Hi! I noticed there hasn’t been any activity here recently. If it’s okay, I’d like to work on this issue. Could you please assign it to me if it’s available?

[tanvikapandey7]

Hi!@northdpole .I'd like to work on this issue. Could you please assign it to me? Ill make sure to submit a clean PR with tests and documentation .

[muskan013-byte]

Hi @northdpole @filipposfwt

I’d like to work on this issue. I plan to reproduce the problem and add proper validation for the CSV import along with clearer error handling.

Could you please assign this issue to me? Thanks!

[AyeshaaRafaqat]

Hi @northdpole I'd like to work on this. I can reproduce both issues (malformed CRE column format and triple quoted text being treated as root CRE) and implement proper input validation with descriptive error messages. Could you assign this to me?