I posted this earlier on SuperUser, but realized that this is likely the more appropriate forum for my question.
We have several thousand very large MP4 files that have been encoded over the past decade using Sorenson Squeeze. Over the past year, there are suddenly a growing number of customers (Universities) with Network/Proxy Server that are suddenly unable to view the videos due to vulnerability described at this link: Apple QuickTime Vulnerability.
Forgive me, I know very little about media and encoding, only that the problem has suddenly started appearing while they view our videos (we use JWPlayer v7 with files hosted at AWS/S3/Cloudfront).
Is there an alternate way of encoding h.264/MP4 that doesn't include any reference or codecs, or whatever it is that flags them as Quicktime files, or some other way to get around this?
Note: Our site streams the h.264 MP4 files with JWPlayer - the end users don't open them with Apple Quicktime.
Partial ffmpeg Output for one of the videos in question:
"format": {
"filename": "c:\\videos\\ABC-123.mp4",
"nb_streams": 4,
"nb_programs": 0,
"format_name": "mov,mp4,m4a,3gp,3g2,mj2",
"format_long_name": "QuickTime / MOV",
"start_time": "0.000000",
"duration": "1632.480000",
"size": "86937415",
"bit_rate": "426038",
"probe_score": 100,
"tags": {
"major_brand": "mp42",
"minor_version": "0",
"compatible_brands": "mp42isomavc1",
"creation_time": "2011-07-13 14:02:44",
"compilation": "0",
"encoder": "Sorenson Squeeze 5.0"
}
rnet
boxes in MP4. Those are not a mandatory spec of the MP4 file format. In fact, ffmpeg does not write those, so any MP4 files rewrapped with ffmpeg should be exploit-shielded. If the MP4s are still being flagged then your malware detector has a very broad trigger - maybe it's just looking at the extension.