@zerothreatai/vulnerability-registry 4.0.0 → 5.0.0

package/dist/categories/authentication.js

@@ -9,7 +9,7 @@ export const AUTH_VULNERABILITIES = {
     // JWT VULNERABILITIES
     // ========================================
     [VulnerabilityCode.JWT_NONE_ALGORITHM]: {
-        id: 57,
+        id: 100,
         code: VulnerabilityCode.JWT_NONE_ALGORITHM,
         title: 'JWT Vulnerability - None Algorithm Attack',
         description: 'Critical JWT vulnerability where the server accepts tokens with "alg": "none" in the header, allowing attackers to forge valid tokens without knowing the secret key by simply removing the signature and modifying claims to impersonate any user including administrators.',
@@ -31,7 +31,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Explicitly specify allowed algorithms during JWT verification and reject "none". Use libraries that do not support "none" algorithm. Always validate the algorithm header against expected values.',
     },
     [VulnerabilityCode.JWT_WEAK_SECRET]: {
-        id: 58,
+        id: 101,
         code: VulnerabilityCode.JWT_WEAK_SECRET,
         title: 'JWT Vulnerability - Weak Secret Key',
         description: 'JWT implementation using a weak or common secret key for HMAC signature verification that can be brute-forced or found in common secret dictionaries, allowing attackers to forge arbitrary valid tokens and bypass authentication to access any user account.',
@@ -53,7 +53,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Use cryptographically strong random secrets of at least 256 bits. Consider using asymmetric algorithms (RS256, ES256) instead of HMAC. Rotate secrets periodically.',
     },
     [VulnerabilityCode.JWT_KEY_CONFUSION]: {
-        id: 59,
+        id: 102,
         code: VulnerabilityCode.JWT_KEY_CONFUSION,
         title: 'JWT Vulnerability - Algorithm Confusion Attack',
         description: 'JWT key confusion vulnerability where the server public key can be used as an HMAC secret by switching the algorithm from RS256 to HS256, allowing attackers to forge valid tokens using the publicly available key to generate valid HMAC signatures.',
@@ -78,7 +78,7 @@ export const AUTH_VULNERABILITIES = {
     // BROKEN ACCESS CONTROL
     // ========================================
     [VulnerabilityCode.BAC_ANONYMOUS_ACCESS]: {
-        id: 60,
+        id: 103,
         code: VulnerabilityCode.BAC_ANONYMOUS_ACCESS,
         title: 'Broken Access Control - Anonymous Access',
         description: 'Critical broken access control vulnerability where authenticated endpoints can be accessed without any authentication by simply removing auth headers or cookies, exposing sensitive functionality and data to unauthenticated attackers without any credential requirement.',
@@ -100,7 +100,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Enforce authentication checks on all protected endpoints. Implement deny-by-default access control. Verify authentication state server-side before processing any request.',
     },
     [VulnerabilityCode.BAC_IDOR]: {
-        id: 61,
+        id: 104,
         code: VulnerabilityCode.BAC_IDOR,
         title: 'Broken Access Control - Insecure Direct Object Reference',
         description: 'IDOR vulnerability where users can access or modify resources belonging to other users by manipulating predictable identifiers like sequential IDs in URLs or request parameters, without proper authorization checks verifying resource ownership.',
@@ -122,7 +122,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Implement proper authorization checks verifying resource ownership. Use unpredictable identifiers (UUIDs). Apply consistent access control policies across all endpoints.',
     },
     [VulnerabilityCode.BAC_VERTICAL_PRIVILEGE]: {
-        id: 62,
+        id: 105,
         code: VulnerabilityCode.BAC_VERTICAL_PRIVILEGE,
         title: 'Broken Access Control - Vertical Privilege Escalation',
         description: 'Vertical privilege escalation vulnerability allowing regular users to access or perform administrative functions by directly accessing admin endpoints or manipulating role/permission parameters, bypassing role-based access controls to gain elevated privileges.',
@@ -147,7 +147,7 @@ export const AUTH_VULNERABILITIES = {
     // MASS ASSIGNMENT
     // ========================================
     [VulnerabilityCode.MASSASSIGN_ROLE_ESCALATION]: {
-        id: 63,
+        id: 106,
         code: VulnerabilityCode.MASSASSIGN_ROLE_ESCALATION,
         title: 'Mass Assignment - Role Escalation',
         description: 'Mass assignment vulnerability allowing attackers to escalate privileges by including additional parameters like "role", "isAdmin", or "permissions" in requests that the application binds to user objects without proper allowlist filtering of settable fields.',
@@ -169,7 +169,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Use allowlist of permitted fields for each endpoint. Implement separate DTOs for input binding. Never auto-bind request data to domain objects without explicit field selection.',
     },
     [VulnerabilityCode.MASSASSIGN_PROTOTYPE_POLLUTION]: {
-        id: 64,
+        id: 107,
         code: VulnerabilityCode.MASSASSIGN_PROTOTYPE_POLLUTION,
         title: 'Mass Assignment - Prototype Pollution',
         description: 'JavaScript prototype pollution vulnerability through mass assignment where attackers inject __proto__ or constructor.prototype properties that modify the Object prototype globally, potentially leading to denial of service, security bypass, or remote code execution.',
@@ -191,7 +191,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Freeze Object.prototype. Use Object.create(null) for objects used as maps. Filter __proto__ and constructor properties from user input. Use --frozen-intrinsics Node.js flag.',
     },
     [VulnerabilityCode.JWT_EXPIRED_TOKEN]: {
-        id: 65,
+        id: 108,
         code: VulnerabilityCode.JWT_EXPIRED_TOKEN,
         title: 'JWT Vulnerability - Expired Token Accepted',
         description: 'JWT implementation does not properly validate token expiration (exp claim), accepting expired tokens that should be rejected. This allows attackers with previously captured tokens to reuse them indefinitely, maintaining unauthorized access without credential updates.',
@@ -213,7 +213,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Always validate exp claim during token verification. Set appropriate token lifetimes. Implement token refresh mechanisms. Use server-side session invalidation for immediate revocation.',
     },
     [VulnerabilityCode.JWT_MISSING_CLAIMS]: {
-        id: 66,
+        id: 109,
         code: VulnerabilityCode.JWT_MISSING_CLAIMS,
         title: 'JWT Vulnerability - Missing Required Claims',
         description: 'JWT tokens are missing critical security claims like exp (expiration), iat (issued at), nbf (not before), or iss (issuer), reducing the security guarantees of the token system and potentially allowing token reuse, replay attacks, or cross-tenant access.',
@@ -235,7 +235,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Include and validate all standard claims: exp, iat, nbf, iss, aud, sub. Define required claims for your application. Reject tokens missing mandatory claims.',
     },
     [VulnerabilityCode.BAC_HORIZONTAL_PRIVILEGE]: {
-        id: 67,
+        id: 110,
         code: VulnerabilityCode.BAC_HORIZONTAL_PRIVILEGE,
         title: 'Broken Access Control - Horizontal Privilege Escalation',
         description: 'Horizontal privilege escalation vulnerability where authenticated users can access data or perform actions belonging to other users at the same privilege level by manipulating user identifiers, object references, or session parameters without ownership verification.',
@@ -257,7 +257,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Implement record-level authorization checks. Verify resource ownership against the authenticated user session. Use indirect references that map to actual resources server-side.',
     },
     [VulnerabilityCode.MASSASSIGN_HIDDEN_FIELD]: {
-        id: 68,
+        id: 111,
         code: VulnerabilityCode.MASSASSIGN_HIDDEN_FIELD,
         title: 'Mass Assignment - Hidden Field Manipulation',
         description: 'Mass assignment vulnerability where attackers can modify hidden form fields or server-side computed values like price, discount, userId, or timestamp by including them in request bodies, bypassing UI restrictions to manipulate business logic or data integrity.',
@@ -279,7 +279,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Never trust client-provided values for server-computed fields. Use explicit DTOs with allowlisted fields. Recompute amounts, timestamps, and IDs server-side.',
     },
     [VulnerabilityCode.JWT_CLAIM_TAMPERING]: {
-        id: 131,
+        id: 112,
         code: VulnerabilityCode.JWT_CLAIM_TAMPERING,
         title: 'JWT - Claim Tampering',
         description: 'JWT claim tampering vulnerability where attackers can modify token claims such as roles, user IDs, or permissions and the server accepts the tampered token, enabling privilege escalation or unauthorized access.',
@@ -301,7 +301,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Validate JWT signatures using strong algorithms and trusted keys. Reject unsigned or weakly signed tokens. Enforce claim validation and server-side authorization checks.',
     },
     [VulnerabilityCode.JWT_KID_INJECTION]: {
-        id: 132,
+        id: 113,
         code: VulnerabilityCode.JWT_KID_INJECTION,
         title: 'JWT - KID Header Injection',
         description: 'JWT key identifier (kid) injection vulnerability where attackers manipulate the kid header to influence key selection or file paths, potentially bypassing signature verification or loading attacker-controlled keys.',
@@ -323,7 +323,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Avoid direct use of kid as a file path or URL. Use a strict allowlist of key IDs and map to known keys in configuration. Reject unexpected or oversized kid values.',
     },
     [VulnerabilityCode.JWT_JKU_INJECTION]: {
-        id: 133,
+        id: 114,
         code: VulnerabilityCode.JWT_JKU_INJECTION,
         title: 'JWT - JKU Header Injection',
         description: 'JWT JKU (JWK Set URL) header injection vulnerability where attackers can control the URL used to fetch signing keys, allowing them to supply their own keys and forge valid tokens.',
@@ -345,7 +345,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Ignore untrusted JKU values or restrict to a strict allowlist of trusted JWKS endpoints. Pin keys or use local key material where possible.',
     },
     [VulnerabilityCode.JWT_EMBEDDED_JWK]: {
-        id: 134,
+        id: 115,
         code: VulnerabilityCode.JWT_EMBEDDED_JWK,
         title: 'JWT - Embedded JWK Injection',
         description: 'JWT embedded JWK vulnerability where attackers include their own JWK in the token header and the server accepts it as a trusted signing key, enabling forged tokens and authentication bypass.',
@@ -367,7 +367,7 @@ export const AUTH_VULNERABILITIES = {
         remediation: 'Reject embedded JWKs from tokens unless explicitly required and validated against a trusted key set. Use pinned keys and strict header validation.',
     },
     [VulnerabilityCode.JWT_X5C_INJECTION]: {
-        id: 135,
+        id: 116,
         code: VulnerabilityCode.JWT_X5C_INJECTION,
         title: 'JWT - X5C Header Injection',
         description: 'JWT x5c header injection vulnerability where attackers provide an untrusted certificate chain, allowing them to influence key selection or bypass signature validation if certificate trust is not strictly enforced.',