I failed an interview once because they wanted to see me understand an admittedly small codebase before making a change. But my experience is that it's better to jump to where the bug obviously is and do the obvious fix and then see what comes out of that--precisely for the reasons you say.

And a codebase doesn't have to be all that big before it's too big for you to understand every possible impact.