MétaCan
Menu
Back to cohort
Record W2181718109 · doi:10.1109/iemcon.2015.7344461

Evaluation of an OAuth 2.0 protocol implementation for web server applications

2015· article· en· W2181718109 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicWeb Application Security Vulnerabilities
Canadian institutionsWestern University
Fundersnot available
KeywordsComputer scienceServerWeb serverProtocol (science)AuthorizationWeb applicationApplication serverExploitWeb serviceComputer securityWorld Wide WebDatabaseThe Internet

Abstract

fetched live from OpenAlex

OAuth 2.0 is one of the protocols that are most commonly implemented as an authorization framework currently. This is because it has many advantages, one of which is its ability to be flexibly implemented on different systems and for different purposes. This work evaluates the implementation of Google's OAuth 2.0 for web server applications. This evaluation indicates that the implementation of Google's OAuth 2.0 protocol may lead to a security flaw that exploits low to medium size web servers. This threat might occur by exhausting the storage resources of the web server and making its applications unavailable. In addition, a number of recommendations are made to help protect against this type of threat when an OAuth 2.0 authorization protocol is implemented on web application servers.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.727
Threshold uncertainty score0.284

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.144
GPT teacher head0.448
Teacher spread0.305 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Quick stats

Citations13
Published2015
Admission routes1
Has abstractyes

Explore more

Same topicWeb Application Security VulnerabilitiesFrench-language works237,207