What's supposed to happen is that you explore why some people think it's a low point task and others think it's a high point task.

Typically you'll either find some rats nest of complexity that the low-pointers hadn't thought about/didn't know about: result? Go with the high estimate and the low pointers learn something. Or, you'll find that the high-pointer assumed something was in-scope that isn't: result? Go with the lower estimate and tighten up the story spec with some non-goals and maybe a link to pre-existing done-work.

I've seen the version you describe, but only in dysfunctional companies. There's no helping those people but Scrum isn't the problem per se.