Defined in 2 files
Last patched
expireByIntent in cloudfoundry/uaa was changed by 1 published CVE fixes in 2017, in 4 distinct patches that added or removed 6 lines in total.
The name occurs in 2 files: server/src/main/java/org/cloudfoundry/identity/uaa/codestore/InMemoryExpiringCodeStore.java, server/src/main/java/org/cloudfoundry/identity/uaa/codestore/JdbcExpiringCodeStore.java.
cloudfoundry/uaa has 19 CVEs with a located fix in total, so 5% of them touched this function.
Every published CVE whose fix changed expireByIntent, newest first, with the lines each fix touched.
CVE-2017-4991 · server/src/main/java/org/cloudfoundry/identity/uaa/codestore/InMemoryExpiringCodeStore.java · lines 83–84 · +2 −2
CVE-2017-4991 · server/src/main/java/org/cloudfoundry/identity/uaa/codestore/JdbcExpiringCodeStore.java · line 141 · +1 −1
Get an alert when the next CVE fix lands in cloudfoundry/uaa, with the patched functions.
Monitor uaa CVEsFunctions in the same files that CVE fixes also changed.
Functions in cloudfoundry/uaa changed by the most CVE fixes.
Common questions about CVE fixes to expireByIntent.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
