Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix JSON panic #4042

Merged
merged 1 commit into from
Apr 19, 2017
Merged

Fix JSON panic #4042

merged 1 commit into from
Apr 19, 2017

Conversation

tsg
Copy link
Contributor

@tsg tsg commented Apr 18, 2017

There can be a panic in the JSON decoding code if the input JSON line contains
"null" as a string, because that unmarshals without errors but results in a nil
map.

The added test was panicking before the change.

@tsg tsg added needs_backport PR is waiting to be backported to other branches. review v5.4.0 labels Apr 18, 2017
There can be a panic in the JSON decoding code if the input JSON line contains
"null" as a string, because that unmarshals without errors but results in a nil
map.
@tsg tsg force-pushed the fix_json_panic branch from 72b8600 to 2d73494 Compare April 18, 2017 21:43
Copy link
Member

@andrewkroh andrewkroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Good catch. I'm surprised it didn't panic on line 45 when reading from the nil map.

@ruflin ruflin merged commit aec81e3 into elastic:master Apr 19, 2017
tsg added a commit to tsg/beats that referenced this pull request Apr 19, 2017
There can be a panic in the JSON decoding code if the input JSON line contains
"null" as a string, because that unmarshals without errors but results in a nil
map.
(cherry picked from commit aec81e3)
@tsg tsg removed the needs_backport PR is waiting to be backported to other branches. label Apr 19, 2017
monicasarbu pushed a commit that referenced this pull request Apr 20, 2017
There can be a panic in the JSON decoding code if the input JSON line contains
"null" as a string, because that unmarshals without errors but results in a nil
map.
(cherry picked from commit aec81e3)
@tsg tsg added the v5.3.2 label Apr 24, 2017
tsg added a commit to tsg/beats that referenced this pull request Apr 24, 2017
There can be a panic in the JSON decoding code if the input JSON line contains
"null" as a string, because that unmarshals without errors but results in a nil
map.
(cherry picked from commit aec81e3)
ruflin pushed a commit that referenced this pull request Apr 24, 2017
There can be a panic in the JSON decoding code if the input JSON line contains
"null" as a string, because that unmarshals without errors but results in a nil
map.
(cherry picked from commit aec81e3)
leweafan pushed a commit to leweafan/beats that referenced this pull request Apr 28, 2023
There can be a panic in the JSON decoding code if the input JSON line contains
"null" as a string, because that unmarshals without errors but results in a nil
map.
(cherry picked from commit f5ad15f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants