Empty strings in some buil-in properties of encrypted OOXML workbook

Aspose.Cells Product Family
1

Hi, Aspose team.

Scenario: The app opens encrypted XLSX files to read built-in properties. Aspose.Cells 24.7.

Issue (actual behavior): Subject and Title built-in properties are empty strings.

Expected behavior: Title property is “LiteraTest”. Subject property is “LiteraTest”. See the attached screenshot.

files.zip (24.1 KB)

Code:

var filePath = "sample.xlsx";
using (var wb = new Workbook(filePath, new LoadOptions(LoadFormat.Xlsx)
{
    Password = "1",
}))
{
    // t and s are empty string
    var t = wb.BuiltInDocumentProperties.Title;
    var s = wb.BuiltInDocumentProperties.Subject;
}

For internal reference: MDP-18515

Thanks.

2

@oleksii88,

Thanks for the template Excel file and screenshot.

After initial testing, I was able to reproduce the issue as you mentioned by using your sample code segment and sample file. I found empty strings retrieved for some built-in properties (e.g, Title, Subject) of the encrypted OOXML workbook.

We require thorough evaluation of the issue. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSNET-56334

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

3

@oleksii88
We are pleased to inform you that your issue (Ticket ID: “CELLSNET-56334”) has been resolved. The fix will be included in the upcoming release (Aspose.Cells v24.8) which we plan to release in the first half of August 2024. We will notify you when the next release is published.

4

@oleksii88
Which tool create this template file?
If we resaved the file with MS Excel, we can not view built-in properties through file properties in Win without MS Excel.
And though we have supported reading your excepted properties, the file saved by us is the same as the result saved by MS Excel.

5

The issues you have found earlier (filed as CELLSNET-56334) have been fixed in this update. This message was posted using Bugs notification tool by johnson.shi