[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f67lw_ykGZuAb2AawrrL-kJl340Fae2_H0Wjfcp8Q3F0":3,"g5a-risk:CVE-2018-25031":149},{"success":4,"data":5,"meta":147},true,{"cveId":6,"title":7,"description":8,"shortDescription":9,"publishedDate":10,"lastModified":11,"cvssScore":12,"cvssVector":13,"cvssMetrics":14,"epssScore":42,"epssPercentile":27,"epssTimeSeries":43,"severity":44,"affectedProducts":45,"affectedProductsCount":51,"references":52,"referencesCount":72,"weaknesses":73,"weaknessesCount":94,"isActivelyExploited":95,"cisaInfo":27,"otxData":27,"relatedBlogPosts":96,"seoMetadata":97,"configurations":122,"relatedVendorCves":131,"notableEvents":132},"CVE-2018-25031","What is CVE-2018-25031?","Swagger UI 4.1.2 and earlier could allow a remote attacker to conduct spoofing attacks. By persuading a victim to open a crafted URL, an attacker could exploit this vulnerability to display remote OpenAPI definitions. Note: This was originally claimed to be resolved in 4.1.3. However, third parties have indicated this is not resolved in 4.1.3 and even occurs in that version and possibly others.","Swagger UI 4.1.2 and earlier could allow a remote attacker to conduct spoofing attacks. By persuading a victim to open a crafted URL, an attacker could explo...","2022-03-11T07:15:07.19","2024-08-01T13:41:41.08",4.3,"CVSS:3.1\u002FAV:N\u002FAC:L\u002FPR:N\u002FUI:R\u002FS:U\u002FC:L\u002FI:N\u002FA:N",{"CVSSMetricV31":15,"CVSSMetricV30":27,"CVSSMetricV2":34,"CVSSMetricV40":27},[16,30],{"Source":17,"Type":18,"CVSSData":19,"ExploitabilityScore":28,"ImpactScore":29},"nvd@nist.gov","Primary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":22,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":26,"ExploitCodeMaturity":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"TemporalSeverity":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":23,"ModifiedAttackVector":27,"ModifiedAttackComplexity":27,"ModifiedPrivilegesRequired":27,"ModifiedUserInteraction":27,"ModifiedScope":27,"ModifiedConfidentialityImpact":27,"ModifiedIntegrityImpact":27,"ModifiedAvailabilityImpact":27,"EnvironmentalScore":27,"EnvironmentalSeverity":27},"3.1","NETWORK","LOW","NONE","REQUIRED","UNCHANGED","MEDIUM",null,2.8,1.4,{"Source":31,"Type":32,"CVSSData":33,"ExploitabilityScore":28,"ImpactScore":29},"134c704f-9b21-4f2e-91b3-4a467353bcc0","Secondary",{"Version":20,"VectorString":13,"AttackVector":21,"AttackComplexity":22,"PrivilegesRequired":23,"UserInteraction":24,"Scope":25,"ConfidentialityImpact":22,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":26,"ExploitCodeMaturity":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"TemporalSeverity":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":23,"ModifiedAttackVector":27,"ModifiedAttackComplexity":27,"ModifiedPrivilegesRequired":27,"ModifiedUserInteraction":27,"ModifiedScope":27,"ModifiedConfidentialityImpact":27,"ModifiedIntegrityImpact":27,"ModifiedAvailabilityImpact":27,"EnvironmentalScore":27,"EnvironmentalSeverity":27},[35],{"Source":17,"Type":18,"CVSSData":36,"BaseSeverity":26,"ExploitabilityScore":40,"ImpactScore":41,"ACInsufInfo":27,"ObtainAllPrivilege":27,"ObtainUserPrivilege":27,"ObtainOtherPrivilege":27,"UserInteractionRequired":4},{"Version":37,"VectorString":38,"AccessVector":21,"AccessComplexity":26,"Authentication":23,"ConfidentialityImpact":39,"IntegrityImpact":23,"AvailabilityImpact":23,"BaseScore":12,"BaseSeverity":27,"Exploitability":27,"RemediationLevel":27,"ReportConfidence":27,"TemporalScore":27,"CollateralDamagePotential":27,"TargetDistribution":27,"ConfidentialityRequirement":27,"IntegrityRequirement":27,"AvailabilityRequirement":27,"EnvironmentalScore":27},"2.0","AV:N\u002FAC:M\u002FAu:N\u002FC:P\u002FI:N\u002FA:N","PARTIAL",8.6,2.9,0.42326,[42,42,42,42,42,42,42],"Medium",[46],{"vendor":47,"product":48,"version":49,"criteria":50,"vulnerable":4},"smartbear","swagger_ui","*","cpe:2.3:a:smartbear:swagger_ui:*:*:*:*:*:*:*:*",1,[53,60,64,68],{"url":54,"source":55,"tags":56},"https:\u002F\u002Fgithub.com\u002Fswagger-api\u002Fswagger-ui\u002Fissues\u002F4872","GitHub",[57,58,59],"Issue Tracking","Patch","Third Party Advisory",{"url":61,"source":55,"tags":62},"https:\u002F\u002Fgithub.com\u002Fswagger-api\u002Fswagger-ui\u002Freleases\u002Ftag\u002Fv4.1.3",[63,59],"Release Notes",{"url":65,"source":66,"tags":67},"https:\u002F\u002Fsecurity.netapp.com\u002Fadvisory\u002Fntap-20220407-0004\u002F","Netapp",[59],{"url":69,"source":70,"tags":71},"https:\u002F\u002Fsecurity.snyk.io\u002Fvuln\u002FSNYK-JS-SWAGGERUI-2314885","Snyk",[58,59],4,[74,82,89],{"id":75,"name":76,"description":77,"extendedDescription":78,"status":79,"abstraction":80,"structure":81},"CWE-20","Improper Input Validation","The product receives input or data, but it does\n        not validate or incorrectly validates that the input has the\n        properties that are required to process the data safely and\n        correctly.","Input validation is a frequently-used technique\n\t   for checking potentially dangerous inputs in order to\n\t   ensure that the inputs are safe for processing within the\n\t   code, or when communicating with other components.  When\n\t   software does not validate input properly, an attacker is\n\t   able to craft the input in a form that is not expected by\n\t   the rest of the application. This will lead to parts of the\n\t   system receiving unintended input, which may result in\n\t   altered control flow, arbitrary control of a resource, or\n\t   arbitrary code execution.\nInput validation is not the only technique for\n\t   processing input, however.  Other techniques attempt to\n\t   transform potentially-dangerous input into something safe, such\n\t   as filtering (CWE-790) - which attempts to remove dangerous\n\t   inputs - or encoding\u002Fescaping (CWE-116), which attempts to\n\t   ensure that the input is not misinterpreted when it is included\n\t   in output to another component. Other techniques exist as well\n\t   (see CWE-138 for more examples.)\nInput validation can be applied to:\nData can be simple or structured.  Structured data\n\t   can be composed of many nested layers, composed of\n\t   combinations of metadata and raw data, with other simple or\n\t   structured data.\nMany properties of raw data or metadata may need\n\t   to be validated upon entry into the code, such\n\t   as:\nImplied or derived properties of data must often\n\t   be calculated or inferred by the code itself.  Errors in\n\t   deriving properties may be considered a contributing factor\n\t   to improper input validation.\nNote that \"input validation\" has very different\n\t   meanings to different people, or within different\n\t   classification schemes.  Caution must be used when\n\t   referencing this CWE entry or mapping to it.  For example,\n\t   some weaknesses might involve inadvertently giving control\n\t   to an attacker over an input when they should not be able\n\t   to provide an input at all, but sometimes this is referred\n\t   to as input validation.\nFinally, it is important to emphasize that the\n\t   distinctions between input validation and output escaping\n\t   are often blurred, and developers must be careful to\n\t   understand the difference, including how input validation\n\t   is not always sufficient to prevent vulnerabilities,\n\t   especially when less stringent data types must be\n\t   supported, such as free-form text. Consider a SQL injection\n\t   scenario in which a person's last name is inserted into a\n\t   query. The name \"O'Reilly\" would likely pass the validation\n\t   step since it is a common last name in the English\n\t   language. However, this valid name cannot be directly\n\t   inserted into the database because it contains the \"'\"\n\t   apostrophe character, which would need to be escaped or\n\t   otherwise transformed. In this case, removing the\n\t   apostrophe might reduce the risk of SQL injection, but it\n\t   would produce incorrect behavior because the wrong name\n\t   would be recorded.","Stable","Class","Simple",{"id":83,"name":84,"description":85,"extendedDescription":86,"status":87,"abstraction":88,"structure":81},"CWE-918","Server-Side Request Forgery (SSRF)","The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.","By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file:\u002F\u002F), or use other protocols such as gopher:\u002F\u002F or tftp:\u002F\u002F, which may provide greater control over the contents of requests.","Incomplete","Base",{"id":90,"name":91,"description":92,"extendedDescription":93,"status":87,"abstraction":80,"structure":81},"CWE-922","Insecure Storage of Sensitive Information","The product stores sensitive information without properly limiting read or write access by unauthorized actors.","If read access is not properly restricted, then attackers can steal the sensitive information. If write access is not properly restricted, then attackers can modify and possibly delete the data, causing incorrect results and possibly a denial of service.",3,false,[],{"title":98,"metaDescription":99,"keywords":100,"canonicalUrl":101,"structuredData":102},"What is CVE-2018-25031? Vulnerability Analysis | Security Advisory | Precursor Intelligence","Comprehensive analysis of CVE-2018-25031, a medium severity cyber security vulnerability from 2022. High exploit probability (42.3%). Swagger UI 4.1.2 and ea...","CVE-2018-25031, CVE-2018-25031 vulnerability, CVE-2018-25031 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research, vulnerability assessment, cyber threats, 2022, CVSS score, exploit, patch, remediation, smartbear security, swagger_ui vulnerability, high risk vulnerability, actively exploited, exploit available","\u002Fwhat-is\u002Fcve-2018-25031",{"@context":103,"@type":104,"headline":98,"description":99,"datePublished":10,"dateModified":11,"author":105,"publisher":109,"about":113,"mainEntityOfPage":117,"articleSection":120,"keywords":121},"https:\u002F\u002Fschema.org","TechArticle",{"@type":106,"name":107,"url":108},"Organization","Precursor Intelligence","https:\u002F\u002Fprecursorintelligence.com",{"@type":106,"name":107,"url":108,"logo":110},{"@type":111,"url":112},"ImageObject","https:\u002F\u002Fprecursorintelligence.com\u002Fimg\u002Flogos\u002Feplogo.png",{"@type":114,"name":6,"description":115,"additionalType":116},"Thing","Cybersecurity Vulnerability","https:\u002F\u002Fschema.org\u002FSoftwareBug",{"@type":118,"@id":119},"WebPage","https:\u002F\u002Fprecursorintelligence.com\u002Fwhat-is\u002Fcve-2018-25031","Cybersecurity","CVE-2018-25031, CVE-2018-25031 vulnerability, CVE-2018-25031 security, medium severity vulnerability, cybersecurity, vulnerability analysis, security advisory, CVE database, threat intelligence, security research",[123],{"Operator":27,"Negate":27,"Nodes":124},[125],{"Operator":126,"Negate":27,"CPEMatch":127},"OR",[128],{"Vulnerable":4,"Criteria":50,"MatchCriteriaID":129,"VersionStartExcluding":27,"VersionStartIncluding":27,"VersionEndExcluding":130,"VersionEndIncluding":27},"29C4300C-B377-4221-923F-A804BA5A9348","4.1.3",[],[133,140],{"id":134,"eventType":135,"eventTime":136,"details":137,"label":138,"color":139},"38bb1f50-0046-4472-ba03-855ac5308523","LOW_EPSS_DELTA","2025-11-19T04:06:47.20646+00:00","Daily EPSS score decreased by 0.599 on 2023-12-30","EPSS Score Decreased","green",{"id":141,"eventType":142,"eventTime":143,"details":144,"label":145,"color":146},"aa793003-41c8-48c0-ac6b-154c49552b29","HIGH_EPSS_DELTA","2025-11-22T04:06:35.418448+00:00","Daily EPSS score increased by 0.588 on 2023-12-30","EPSS Score Increased","red",{"lastModified":11,"cacheTime":148,"version":37},1792347808952,{"score":150,"band":44,"action":151,"scoredAt":152},40,"Plan remediation","2026-10-16T06:53:48.853738+00:00"]