You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
encoding/protojson: Unmarshal could enter an infinite loop when unmarshaling certain forms of invalid JSON. This condition can occur when unmarshaling into a message which contains a google.protobuf.Any value, or when the UnmarshalOptions.DiscardUnknown option is set. Unmarshal now correctly returns an error when handling these inputs. This is CVE-2024-24786.
Announcement
In the previous two releases, v1.29.0 and v1.29.1, we associated the tags with the wrong commits and thus the tags do not reference any commit in this repository. This tag, v1.30.0, refers to an existing commit again. Sorry for the inconvenience.
Notable changes
New Features
CL/449576: protoadapt: helper functions to convert v1 or v2 message to either v1 or v2 message.
This version introduces a new package protodelim to marshal and unmarshal size-delimited messages.
It also brings the implementation up to date with the latest protobuf features.
CL/462315: cmd/protoc-gen-go: make deprecated messages more descriptive
CL/473015: encoding/prototext: allow whitespace and comments between minus sign and number in negative numeric literal
Alignment with protobuf
CL/426054: types/descriptorpb: update *.pb.go to use latest protoc release, 21.5
CL/425554: encoding/protojson: fix parsing of google.protobuf.Timestamp
CL/461238: protobuf: remove the check for reserved field numbers
CL/469255: types/descriptorpb: regenerate using latest protobuf v22.0 release
CL/472696: cmd/protoc-gen-go: support protobuf retention feature
Documentation improvements:
CL/464275: proto: document Equal behavior of invalid messages
CL/466375: all: update links to Protocol Buffer documentation
Minor performance improvements
CL/460215: types/known/structpb: preallocate map in AsMap
CL/465115: internal/strs: avoid unnecessary allocations in Builder
Breaking changes
CL/461238: protobuf: remove the check for reserved field numbers
protowire.(Number).IsValid() no longer returns false for reserved fields because reserved fields are considered semantically valid by the protobuf spec.
If you want to rebase/retry this PR, check this box
This pull request has been automatically flagged for inactivity because it has not been acted upon in the last 60 days. It will be closed if no new activity occurs in the next 30 days. Please feel free to re-open to resurrect the change if you feel this has happened by mistake. Thank you for your contributions.
Closing due to inactivity. If you feel this was a mistake or you wish to re-open at any time in the future, please leave a comment and it will be re-surfaced for the maintainers to review.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.28.1
->v1.33.0
By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
protocolbuffers/protobuf-go (google.golang.org/protobuf)
v1.33.0
Compare Source
This release contains one security fix:
encoding/protojson
:Unmarshal
could enter an infinite loop when unmarshaling certain forms of invalid JSON. This condition can occur when unmarshaling into a message which contains agoogle.protobuf.Any
value, or when theUnmarshalOptions.DiscardUnknown
option is set.Unmarshal
now correctly returns an error when handling these inputs. This is CVE-2024-24786.v1.32.0
Compare Source
Full Changelog: protocolbuffers/protobuf-go@v1.31.0...v1.32.0
This release contains commit protocolbuffers/protobuf-go@bfcd647, which fixes a denial of service vulnerability by preventing a stack overflow through a default maximum recursion limit. See https://github.com/golang/protobuf/issues/1583 and https://github.com/golang/protobuf/issues/1584 for details.
v1.31.0
Compare Source
Notable changes
New Features
Minor performance improvements
Bug fixes
v1.30.0
Compare Source
Announcement
In the previous two releases, v1.29.0 and v1.29.1, we associated the tags with the wrong commits and thus the tags do not reference any commit in this repository. This tag, v1.30.0, refers to an existing commit again. Sorry for the inconvenience.
Notable changes
New Features
v1.29.1
Compare Source
Notable changes
Bug fixes
v1.29.0
Compare Source
Overview
This version introduces a new package
protodelim
to marshal and unmarshal size-delimited messages.It also brings the implementation up to date with the latest protobuf features.
Notable changes
New Features
Alignment with protobuf
Documentation improvements:
Minor performance improvements
Breaking changes