So, what's the story?
CVE-2018-0370, BugID CSCvi09219 describes affected and fixed software in the same version:
Awesome. That makes a ton of sense :/
Link to the tool for this bug here: CSCvi09219
I have a TAC case open to clarify, they don't know either after two days of owning it.
The bug is not discussed in the FMC Virtual release notes for 6.2.3.1, 6.2.3.2, 6.2.3.3.
If anybody knows the story that would be great.
