diff --git a/crates/http/RUSTSEC-0000-0000.toml b/crates/http/RUSTSEC-0000-0000.toml
deleted file mode 100644
index 4d9b3cd..0000000
--- a/crates/http/RUSTSEC-0000-0000.toml
+++ /dev/null
@@ -1,79 +0,0 @@
-# Before you submit a PR using this template, **please delete the comments**
-# explaining each field, as well as any unused fields.
-
-[advisory]
-# Identifier for the advisory (mandatory). Will be assigned a "RUSTSEC-YYYY-NNNN"
-# identifier e.g. RUSTSEC-2018-0001. Please use "RUSTSEC-0000-0000" in PRs.
-id = "RUSTSEC-0000-0000"
-
-# Name of the affected crate (mandatory)
-package = "http"
-
-# Disclosure date of the advisory as an RFC 3339 date (mandatory)
-date = "2019-11-16"
-
-# Single-line description of a vulnerability (mandatory)
-title = "Integer Overflow in HeaderMap::reserve() can cause Denial of Service"
-
-# Enter a short-form description of the vulnerability here (mandatory)
-description = """
-`HeaderMap::reserve()` used `usize::next_power_of_two()` to calculate the increased capacity.
-However, `next_power_of_two()` silently overflows to 0 if given a sufficently large number
-in release mode.
-
-If the map was not empty when the overflow happens,
-the library will invoke `self.grow(0)` and start infinite probing.
-This allows an attacker who controls the argument to `reserve()`
-to cause a potential denial of service (DoS).
-
-The flaw was corrected in 0.2.0 release of `http` crate.
-"""
-
-# Versions which include fixes for this vulnerability (mandatory)
-patched_versions = [">= 0.2.0"]
-
-# Versions which were never vulnerable (optional)
-#unaffected_versions = ["< 1.1.0"]
-
-# URL to a long-form description of this issue, e.g. a GitHub issue/PR,
-# a change log entry, or a blogpost announcing the release (optional)
-url = "https://github.com/hyperium/http/issues/352"
-
-# Optional: Categories this advisory falls under. Valid categories are:
-# "code-execution", "crypto-failure", "denial-of-service", "file-disclosure"
-# "format-injection", "memory-corruption", "memory-exposure", "privilege-escalation"
-categories = ["denial-of-service"]
-
-# Freeform keywords which describe this vulnerability, similar to Cargo (optional)
-keywords = ["http", "integer-overflow", "DoS"]
-
-# Vulnerability aliases, e.g. CVE IDs (optional but recommended)
-# Request a CVE for your RustSec vulns: https://iwantacve.org/
-#aliases = ["CVE-2018-XXXX"]
-
-# References to related vulnerabilities (optional)
-# e.g. CVE for a C library wrapped by a -sys crate)
-#references = ["CVE-2018-YYYY", "CVE-2018-ZZZZ"]
-
-# Optional: metadata which narrows the scope of what this advisory affects
-[affected]
-# CPU architectures impacted by this vulnerability (optional).
-# Only use this if the vulnerability is specific to a particular CPU architecture,
-# e.g. the vulnerability is in x86 assembly.
-# For a list of CPU architecture strings, see the "platforms" crate:
-# <https://docs.rs/platforms/latest/platforms/target/enum.Arch.html>
-#arch = ["x86", "x86_64"]
-
-# Operating systems impacted by this vulnerability (optional)
-# Only use this if the vulnerable is specific to a particular OS, e.g. it was
-# located in a binding to a Windows-specific API.
-# For a list of OS strings, see the "platforms" crate:
-# <https://docs.rs/platforms/latest/platforms/target/enum.OS.html>
-#os = ["windows"]
-
-# Table of canonical paths to vulnerable functions (optional)
-# mapping to which versions impacted by this advisory used that particular
-# name (e.g. if the function was renamed between versions). 
-# The path syntax is `cratename::path::to::function`, without any
-# parameters or additional information, followed by a list of version reqs.
-functions = { "http::header::HeaderMap::reserve" = ["< 0.2.0"] }
\ No newline at end of file
diff --git a/crates/http/RUSTSEC-2019-0033.toml b/crates/http/RUSTSEC-2019-0033.toml
new file mode 100644
index 0000000..12170fd
--- /dev/null
+++ b/crates/http/RUSTSEC-2019-0033.toml
@@ -0,0 +1,24 @@
+[advisory]
+id = "RUSTSEC-2019-0033"
+package = "http"
+date = "2019-11-16"
+title = "Integer Overflow in HeaderMap::reserve() can cause Denial of Service"
+description = """
+`HeaderMap::reserve()` used `usize::next_power_of_two()` to calculate the increased capacity.
+However, `next_power_of_two()` silently overflows to 0 if given a sufficently large number
+in release mode.
+
+If the map was not empty when the overflow happens,
+the library will invoke `self.grow(0)` and start infinite probing.
+This allows an attacker who controls the argument to `reserve()`
+to cause a potential denial of service (DoS).
+
+The flaw was corrected in 0.2.0 release of `http` crate.
+"""
+patched_versions = [">= 0.2.0"]
+url = "https://github.com/hyperium/http/issues/352"
+categories = ["denial-of-service"]
+keywords = ["http", "integer-overflow", "DoS"]
+
+[affected.functions]
+"http::header::HeaderMap::reserve" = ["< 0.2.0"]