Upstream information
Description
Net::OAuth versions before 0.33 for Perl allow the sender to choose the signature algorithm in verify.verify resolves the signature method class from the signature_method parameter of the incoming message. signature_method is required on every request, so the algorithm used to check a signature is chosen by whoever sent it, and nothing lets the verifying party pin the method instead. When a message names HMAC-SHA1 or HMAC-SHA256, the key is derived from consumer_secret and token_secret rather than from the key the provider deployed.
A provider deployed on RSA-SHA1 holds only the consumer public key, and RFC 5849 does not use consumer_secret for that method, so the required parameter is filled with a placeholder. A client that names HMAC-SHA1 instead has its signature checked against that placeholder, so a guessable one is enough to forge requests for any consumer key and token.
SUSE information
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
SUSE Bugzilla entry: 1275759 [NEW] No SUSE Security Announcements cross referenced.List of released packages
| Product(s) | Fixed package version(s) | References |
|---|---|---|
| openSUSE Tumbleweed |
| Patchnames: openSUSE-Tumbleweed-2026-11551 |
SUSE Timeline for this CVE
CVE page created: Thu Aug 20 21:16:34 2026CVE page last modified: Thu Aug 20 21:16:34 2026