rsync and librsync collisions

2014.10.13

Credit: Martin

Risk: Medium

Local: No

Remote: Yes

CVE: CVE-2014-8242

CWE: N/A

Ogólna skala CVSS: 5.8/10

Znaczenie: 4.9/10

Łatwość wykorzystania: 8.6/10

Wymagany dostęp: Zdalny

Złożoność ataku: Średnia

Autoryzacja: Nie wymagana

Wpływ na poufność: Brak

Wpływ na integralność: Częściowy

Wpływ na dostępność: Częściowy

Hi,
I'm the librsync (not rsync) maintainer. I can confirm this is a real bug,
and I would like a CVE assigned.
I appreciate Mik reporting this.
Since it's now been discussed in public I don't see any point treating this
as embargoed.
I'm working on his patch adding BLAKE2 (eg making it pass tests, having an
option for back-compatibility) so that it can be released.
-m

Referencje:

http://seclists.org/oss-sec/2014/q4/309

See this note in RAW Version

Vote for this issue:

50%

Thanks for you vote!

Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.

Nick (*)

Email (*)

Video

Text (*)

(*) - required fields.

{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1

{{ x.comment }}

rsync and librsync collisions

Referencje:

Thanks for you vote!

Thanks for you comment!Your message is in quarantine 48 hours.

Thanks for you comment!
Your message is in quarantine 48 hours.