Raphaël Vinot

Right, confirmed: creating the object doesn't require `meta-category`/`description`/`template_uuid` but update doesn't work. That should probably be fixed on MISP site. In the meantime, I'd strongly recommend you to create a...

Good catch, let's see what @mokaddem and @iglocska say, there might be a reason I'm not aware of to have that. I'm a bit worried about the vast amount of...

You're welcome, and let us know if you have further questions!

Yeah, this method is meant for the UI, not for the API, we need to implement something specific for the API. My guess regarding the time is that as it...

I think the problem is due to the fact your manifest file is a list of dictionaries, when is should just be a dictionary. Your manifest file should look like...

Oh wow, nice catch. Let me loop @iglocska in for that one, because I'm unsure about the way forward, and if/how we can fix it.

It is currently not implemented in PyMISP. I'll try to work on it soon-ish.

That's annoying. I think the only realistic solution is to add another `object_relation` called `vulnerable_configuration` because if we only rename it in the template, the objects created with `vulnerable-configuration` will...

Okay, this is even more confusing: PyMISP should already support the objects coming from old templates. Then I look at the event `30839540-715f-46fa-9fe3-a3b0b441d01e`, I cannot find any `object_relation` called `vulnerable_configuration`...

So yes and no. [This module](https://github.com/MISP/misp-modules/blob/main/misp_modules/modules/expansion/cve_advanced.py#L51) is pushing objects with the old format. PyMISP logs it [as a warning](https://github.com/MISP/PyMISP/blob/main/pymisp/mispevent.py#L1032) but doesn't block it (it is in line with how MISP...