dlt_config_file_parser.c：Fix a pointer release bug in the file。

[Leslie-bcy]

In the dlt_config_file_set_section function of dlt_config_file_parser.c, the following code exists:

s-name is not set to null after free.

It will be freed again in the dlt_config_file_release function.

[thanhbnq]

Thanks @Safe-BCY ,
I strongly believe that the commit message should be updated instead of only "bb".
Please kindly update (please refer to other commits for format)
Thanh

[Leslie-bcy]

Thank you, I will resubmit according to the format.

[Leslie-bcy]

Thanks @Safe-BCY , I strongly believe that the commit message should be updated instead of only "bb". Please kindly update (please refer to other commits for format) Thanh

The format has been modified as required, please check。

[Leslie-bcy]

further information：The Same pointer（s->name）is freed again in the dlt_config_file _release。

void dlt_config_file_release(DltConfigFile *file)
{
int i = 0;

if (file != NULL) {
    int max = file->num_sections;

    for (i = 0; i < max; i++) {
        DltConfigFileSection *s = &file->sections[i];
        DltConfigKeyData *node = file->sections[i].list;
        free(s->name);    //free again。

        if (s->keys != NULL)
            free(s->keys);

        while (node) {
            DltConfigKeyData *tmp = node;
            node = node->next;
            free(tmp->key);
            free(tmp->data);
            free(tmp);
        }
    }

    free(file->sections);
    free(file);
}

}

[thanhbnq]

@Safe-BCY
Well, it looks like you just update information in your comment, not about the commit message itself.
We still see same as before. You can check via tab "Commits" in this PR.
Thank you,
Thanh

[Leslie-bcy]

@Safe-BCY Well, it looks like you just update information in your comment, not about the commit message itself. We still see same as before. You can check via tab "Commits" in this PR. Thank you, Thanh

[Leslie-bcy]

Sorry, this is the first time I submit PR.Please see if what I submit now meets the requirements.

[thanhbnq]

@Safe-BCY ,

1. In case you want to update your commit, please update via "amend". Then you will see one commit instead of two now in your develop branch.
2. In your commit message, I think there are several references for you:
   https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53
3. The information in your current commit message could be shared via the conversation of PR. Then you still can keep the commit message clean, short and informative.
4. Please add sign-off at the end of git commit message.

Thank you,
Thanh

[Leslie-bcy]

Thank you. I have revised it again. Please check it, please.

[thanhbnq]

@Safe-BCY
It is good now. Thank you very much!

[Leslie-bcy]

@Safe-BCY It is good now. Thank you very much!

May I ask if you can help apply for CVE number?

[Leslie-bcy]

@thanhbnq May I ask if you can help apply for CVE number?

[carnil]

CVE-2022-31291 seems to have been assigned for this issue.

[Leslie-bcy]

CVE-2022-31291 seems to have been assigned for this issue.

Thank you.